> On 25 Feb 2024, at 14:04, Marcos Pegoraro wrote:
> There are lots of new functions and better explanations of old features.
> Then my question is, how to know all pages which were changed and what
> exactly was changed on those pages ?
Which problem are you trying to solve? You should be
It's not easy to see what exactly changed between this and that version, on
a specific page on documentation. As an example I got this page but you'll
see this problem anywhere on docs.
https://www.postgresql.org/docs/16/functions-json.html
and
On 2024-02-25 17:38 +0100, Marcos Pegoraro wrote:
> All the time we have doubts about what function exists in what version, or
> was changed.
pgPedia may give you some overview, although it does not claim to be
up-to-date.
> IS JSON belongs to 15 or 16, MERGE was done on 14 or 15, as example,
> On 25 Feb 2024, at 17:38, Marcos Pegoraro wrote:
> So I was thinking of a way to get differences between this and that versions,
> and for all doc pages.
> Something like we already have on [2], it explicits, this feature was
> introduced, this was changed, this does not exist anymore.
The
Hi, I set up logical replication a few days ago, but it's throwing some
weird log lines that have me worried. Does anybody have experience with
lines like the following on a subscriber:
LOG: logical replication table synchronization worker for subscription
"compass_subscription", table
>
> Which problem are you trying to solve? You should be reading the version
> of
> the docs which corresponds to the version you are running. If you are
> trying
> to figure out an upgrade then the release notes are probably a better
> starting
> point.
Daniel Gustafsson
>
All the time we
On 2/25/24 08:38, Marcos Pegoraro wrote:
Which problem are you trying to solve? You should be reading the
version of
the docs which corresponds to the version you are running. If you
are trying
to figure out an upgrade then the release notes are probably a
better
Sorry, two more little things here. The publisher logs add much, but here's
what we see:
STATEMENT: START_REPLICATION SLOT "pg_20031_sync_17418_7324846428853951375"
LOGICAL F1D0/346C6508 (proto_version '2', publication_names
'"compass_publication2"')
ERROR: replication slot
On Sun, Feb 25, 2024 at 1:11 PM Mike Lissner
wrote:
> Sorry, two more little things here. The publisher logs add much, but
> here's what we see:
>
> STATEMENT: START_REPLICATION SLOT
> "pg_20031_sync_17418_7324846428853951375" LOGICAL F1D0/346C6508
> (proto_version '2', publication_names
Hi
po 26. 2. 2024 v 7:28 odesílatel Emiel Mols napsal:
> Hello,
>
> To improve our unit and end-to-end testing performance, we are looking to
> optimize initialization of around 500-1000 database *schemas* from a
> schema.sql file.
>
> Background: in postgres, you cannot change databases on
>
On Sun, 25 Feb, 2024, 1:05 am yudhi s, wrote:
>
> On Fri, Feb 23, 2024 at 5:26 PM sud wrote:
>
>>
>>
>> On Fri, 23 Feb, 2024, 1:28 pm yudhi s,
>> wrote:
>>
>>>
>>>
>>> On Fri, 23 Feb, 2024, 1:20 pm sud, wrote:
>>>
On Fri, 23 Feb, 2024, 12:41 pm Laurenz Albe,
wrote:
Thanks, as indicated we're using that right now. The 30% spinlock overhead
unfortunately persists.
- Fsync was already disabled, too. Complete postgresql.conf used in testing:
listen_addresses = ''
max_connections = 2048
unix_socket_directories = '..'
shared_buffers = 128MB
log_line_prefix = ''
Hello,
To improve our unit and end-to-end testing performance, we are looking to
optimize initialization of around 500-1000 database *schemas* from a
schema.sql file.
Background: in postgres, you cannot change databases on
existing connections, and using schemas would allow us to minimize the
po 26. 2. 2024 v 8:08 odesílatel Emiel Mols napsal:
> Thanks, as indicated we're using that right now. The 30% spinlock overhead
> unfortunately persists.
>
try to increase shared_buffer
128MB can be too low
max_connection = 2048 - it unrealistic high
> - Fsync was already disabled, too.
On Mon, Feb 26, 2024 at 1:49 AM Daniel Gustafsson wrote:
>
> > On 25 Feb 2024, at 17:38, Marcos Pegoraro wrote:
>
> > So I was thinking of a way to get differences between this and that
> > versions, and for all doc pages.
> > Something like we already have on [2], it explicits, this feature
15 matches
Mail list logo
