Not sure if there were other attempts to add something like that, but if they did take place, they were not finalized - pg_dump does not have such option to this day.
#Postgresql
Not sure if there were other attempts to add something like that, but if they did take place, they were not finalized - pg_dump does not have such option to this day.
#Postgresql
There should be a separate third handle, on the inside, dedicated just for testing. That will fix the problem.
Or a hole for the hand for reaching to the outside handle.
I don't get it why they stopped mid way with such clearly incomplete design.
There should be a separate third handle, on the inside, dedicated just for testing. That will fix the problem.
Or a hole for the hand for reaching to the outside handle.
I don't get it why they stopped mid way with such clearly incomplete design.
You've motivated me to take a closer look into the docs, and turns out there is even more nuance to various usages of `-c`, chained `-c`, or just using stdin I wasn't aware of.
Solid tip. 🐘
You've motivated me to take a closer look into the docs, and turns out there is even more nuance to various usages of `-c`, chained `-c`, or just using stdin I wasn't aware of.
Solid tip. 🐘
... like a request for sudo password - if such privilege escalation is requested.
Some more on that here: notes.aflukasz.pl/en/2025/08/0... .
... like a request for sudo password - if such privilege escalation is requested.
Some more on that here: notes.aflukasz.pl/en/2025/08/0... .
This timeout starts counting down approximately at the same time as the connection timeout does (they more or less overlap, starting when connection is being initiated).
It tracks if we are not waiting too long for the privilege escalation prompt to be generated on the remote system...
This timeout starts counting down approximately at the same time as the connection timeout does (they more or less overlap, starting when connection is being initiated).
It tracks if we are not waiting too long for the privilege escalation prompt to be generated on the remote system...
This timeout has a value of the ssh connection timeout (which is configurable and defaults to 10s) extended by adding extra 2 seconds, as seen in github.com/ansible/ansi...:
```
timeout = 2 + self.get_option('timeout')
```
It's not otherwise settable directly.
This timeout has a value of the ssh connection timeout (which is configurable and defaults to 10s) extended by adding extra 2 seconds, as seen in github.com/ansible/ansi...:
```
timeout = 2 + self.get_option('timeout')
```
It's not otherwise settable directly.
Each time I ultimately got this value be creating temporary r2 bucket and extracting id from advertised bucket endpoint url.
@cloudflare.social - I dare you to teach me about my mistakes here.
Each time I ultimately got this value be creating temporary r2 bucket and extracting id from advertised bucket endpoint url.
@cloudflare.social - I dare you to teach me about my mistakes here.
... on freshly created accounts, because the whole page where this id could be obtained is... replaced with a wizard form of sorts for pages product ("Boost your site's speed and security").
But all i need is id to use with their API. ☹️
Recently I was in this situation a couple of times...
... on freshly created accounts, because the whole page where this id could be obtained is... replaced with a wizard form of sorts for pages product ("Boost your site's speed and security").
But all i need is id to use with their API. ☹️
Recently I was in this situation a couple of times...
```
{% if condition %}
setting = {{ val }}
{% else %}
# Skipping setting assignment - condition not met.
{% endif %}
```
Config files typically support comments (right, JSON?). Making else branch explicit that way makes it clear what happened, without a need to consult file generation process.
```
{% if condition %}
setting = {{ val }}
{% else %}
# Skipping setting assignment - condition not met.
{% endif %}
```
Config files typically support comments (right, JSON?). Making else branch explicit that way makes it clear what happened, without a need to consult file generation process.
... and then, when such generated file is read in a different context, outside of a templating process, it's not clear that such decision was actually made or if maybe it was forgotten to be made, never considered when writing the template etc.
Often a better approach would be the following:
... and then, when such generated file is read in a different context, outside of a templating process, it's not clear that such decision was actually made or if maybe it was forgotten to be made, never considered when writing the template etc.
Often a better approach would be the following:
... occurrences of stdin pointed to as a source, this allows, for example, for merging consecutive lines from a single source:
```
$ echo -e "1\n2\n3\n4" | paste - -
1 2
3 4
```
Some more examples at notes.aflukasz.pl/en/2025/07/1... .
... occurrences of stdin pointed to as a source, this allows, for example, for merging consecutive lines from a single source:
```
$ echo -e "1\n2\n3\n4" | paste - -
1 2
3 4
```
Some more examples at notes.aflukasz.pl/en/2025/07/1... .
As per standard (pubs.opengroup.org/onlinepubs/9...): "If '-' is specified for one or more of the files, the standard input shall be used; the standard input shall be read one line at a time, circularly, for each instance of '-'."
So because state (read offset) is shared for all the...
As per standard (pubs.opengroup.org/onlinepubs/9...): "If '-' is specified for one or more of the files, the standard input shall be used; the standard input shall be read one line at a time, circularly, for each instance of '-'."
So because state (read offset) is shared for all the...
... two identical sequences of 8 bytes (one for each column). In this case it's `00 a4 93 d6 00 00 00 00`, which is the number of microseconds between 2000-01-01T00:00:00Z and 2000-01-01T01:00:00Z.
I expand on that some more at notes.aflukasz.pl/en/2025/05/3... .
... two identical sequences of 8 bytes (one for each column). In this case it's `00 a4 93 d6 00 00 00 00`, which is the number of microseconds between 2000-01-01T00:00:00Z and 2000-01-01T01:00:00Z.
I expand on that some more at notes.aflukasz.pl/en/2025/05/3... .
... insert a sample row like `insert into test (tnotz, ttz) values ('2000-01-01 01:00:00', '2000-01-01 01:00:00' at time zone 'utc')`, and then take a look into the table file on disk, you will find that the contents of this row is represented by...
... insert a sample row like `insert into test (tnotz, ttz) values ('2000-01-01 01:00:00', '2000-01-01 01:00:00' at time zone 'utc')`, and then take a look into the table file on disk, you will find that the contents of this row is represented by...
Sorry, recent trauma.
Sorry, recent trauma.
... the data scheme usage itself, but to the embedding of an empty string. Inlining an actual small "empty" image could maybe improve the effect in some cases. Although, arguably, this starts being close to... just having an actual favicon.
... the data scheme usage itself, but to the embedding of an empty string. Inlining an actual small "empty" image could maybe improve the effect in some cases. Although, arguably, this starts being close to... just having an actual favicon.