On Thu, Dec 28, 2023 at 4:54 PM Kaushik Iska wrote:
> Hi all,
>
> I'm including additional details, as I am able to reproduce this issue a
> little more reliably.
>
> Postgres Version: POSTGRES_14_9.R20230830.01_07
> Vendor: Google Cloud SQL
> Logical Replication Protocol version 1
>
> Here are
Hi all,
I'm including additional details, as I am able to reproduce this issue a
little more reliably.
Postgres Version: POSTGRES_14_9.R20230830.01_07
Vendor: Google Cloud SQL
Logical Replication Protocol version 1
Here are the logs of attempt succeeding right after it fails:
2023-12-27
On 12/28/23 12:41, Sean Flaherty wrote:
I'm rather new to the mailing list, are there any additional steps I
should take (i.e. posting to pgsql-hackers, etc.)?
For what purpose? You are seeing differences in compression strategies
between lz4 and pglz. The 'fix' would be to go back to pglz.
I'm rather new to the mailing list, are there any additional steps I should
take (i.e. posting to pgsql-hackers, etc.)?
On Thu, Dec 28, 2023 at 11:23 AM Adrian Klaver
wrote:
> On 12/28/23 09:13, Sean Flaherty wrote:
> > Follow-up:
> > Working with AWS, we found that starting in RDS Postgres
On 12/28/23 09:13, Sean Flaherty wrote:
Follow-up:
Working with AWS, we found that starting in RDS Postgres 15, the
default_toast_compression parameter is set to use lz4 compression
instead of pglz. This resulted in the increased json storage size we
were seeing.
I have been able to
Follow-up:
Working with AWS, we found that starting in RDS Postgres 15, the
default_toast_compression parameter is set to use lz4 compression instead
of pglz. This resulted in the increased json storage size we were seeing.
I have been able to reproduce the increased storage size on RDS Postgres
На нд, 24.12.2023 г. в 3:37 Michael Paquier написа:
> > What quick solution would fix the replication? Repack of the table?
> Reload
> > of the database? Killing some backends?
>
> There may be something you could do as a short-term solution, but it
> does not solve the actual root of the
Hi Thomas,
In case it is helpful for analyzing whats causing the cash, I've
uploaded the db dump I experience the crash on to:
https://drive.google.com/file/d/1H9Y3FaoBafakHwXhpT3s8NNQ1UNJLpJY/view?usp=sharing
The only steps I had to do to trigger the crash were:
- Start with fresh rasperry pi
