On 9/29/21 8:37 PM, Tom Lane wrote:
> Adrian Klaver writes:
>> Unless folks are using plain text only email readers. That is why
>> screenshots are generally a bad idea for textual information. For the
>> record the Postgres version is 12.8.
>
> Hmm, if it's v12 then NodeTag 223 is T_List, which i
Hi. I was playing with the -E option a bit[1]. If I do for example a \d,
the queries and the regular output are interspersed on the screen. I see I
can use \o to send the regular output to a file, leaving only the queries
on the screen. But is there any way to do the reverse (capture the querie
On 9/29/21 8:37 PM, Tom Lane wrote:
Adrian Klaver writes:
Unless folks are using plain text only email readers. That is why
screenshots are generally a bad idea for textual information. For the
record the Postgres version is 12.8.
Hmm, if it's v12 then NodeTag 223 is T_List, which is ... a
Adrian Klaver writes:
> Unless folks are using plain text only email readers. That is why
> screenshots are generally a bad idea for textual information. For the
> record the Postgres version is 12.8.
Hmm, if it's v12 then NodeTag 223 is T_List, which is ... a bit
surprising. That's a common e
Amine Tengilimoglu writes:
> I thought that the server version can be guess from the screenshot . I
> already update the latest minor pg version and it didn't work :)
Some of us aren't in the habit of loading images from external email,
especially not if they're broken attachments as this one was
On 9/29/21 10:54 AM, Amine Tengilimoglu wrote:
I thought that the server version can be guess from the screenshot . I
Unless folks are using plain text only email readers. That is why
screenshots are generally a bad idea for textual information. For the
record the Postgres version is 12.8.
I thought that the server version can be guess from the screenshot . I
already update the latest minor pg version and it didn't work :)
Thank you Tom.
Tom Lane , 29 Eyl 2021 Çar, 20:16 tarihinde şunu yazdı:
> Amine Tengilimoglu writes:
> > I am getting the "ERROR: unrecognized node type:
Amine Tengilimoglu writes:
> I am getting the "ERROR: unrecognized node type: 223" when I execute \d
> combinations in psql and even when getting backup with pg_dump... probably
> the same error will occur with other commands. What is causing this issue,
> any idea? How to fix it?
You're not
Hi;
I am getting the "ERROR: unrecognized node type: 223" when I execute \d
combinations in psql and even when getting backup with pg_dump... probably
the same error will occur with other commands. What is causing this issue,
any idea? How to fix it?
[image: image.png]
If your processes somehow allow updates on the wrong table, then fix that.
If you run out of space in whatever value range you choose initially, the
pain to upgrade to a type that allows larger values would seem to be very
large.
On Wed, 2021-09-29 at 11:26 +0200, Peter J. Holzer wrote:
> I discovered this technique back in my Oracle days but it dropped out of
> my toolbox when I switched to PostgreSQL. Recently I had reason to
> revisit it, so I thought I should share it (trivial though it is).
>
> So the solution is to u
On 2021-09-29 11:42:42 +0200, Tobias Meyer wrote:
> Possible drawbacks:
>
> * The ids will grow faster, and they will be large even on small
> tables. It may be a bit irritating if you have a table with just 5
> rows and the ids are 5, 6, 7, 12654, 345953.
[...]
>
> * you w
>
>
> Possible drawbacks:
>
> * The ids will grow faster, and they will be large even on small
>tables. It may be a bit irritating if you have a table with just 5
>rows and the ids are 5, 6, 7, 12654, 345953.
> * Bottleneck? Using a single sequence was said to be a performance
>bottle
I discovered this technique back in my Oracle days but it dropped out of
my toolbox when I switched to PostgreSQL. Recently I had reason to
revisit it, so I thought I should share it (trivial though it is).
PostgreSQL makes it easy to generate unique ids. Just declare the column
as SERIAL (or IDEN
Is there a solution to use publication/subscription on a master-slave or
primary-standby postgres setup without manual intervention?
Currently the DB clusters are managed by Pacemaker. Once there is a
failover, the pacemaker is able to promote the secondary node to primary,
but the logical replica
15 matches
Mail list logo
