stgresql.org
<mailto:pgsql-general@lists.postgresql.org>
*Subject:* Re: pg_wal fills up on big update query
On Aug 7, 2019, at 7:34 AM, Daniel Fink (PDF) <mailto:daniel.f...@pdf.com>> wrote:
Hi all,
I have a migration where I
·Add a new nullable column to a table
understanding of how postgres works under the hood.
Best Regards,
Daniel
-Original Message-
From: Luca Ferrari [mailto:fluca1...@gmail.com]
Sent: Friday, August 9, 2019 3:58 PM
To: Daniel Fink (PDF)
Cc: pgsql-general
Subject: Re: pg_wal fills up on big update query
On Wed, Aug 7, 2019 at 3:34
...@gmail.com]
*Sent:* Wednesday, August 7, 2019 4:22 PM
*To:* Daniel Fink (PDF)
*Cc:* pgsql-general@lists.postgresql.org
*Subject:* Re: pg_wal fills up on big update query
On Aug 7, 2019, at 7:34 AM, Daniel Fink (PDF) wrote:
Hi all,
I have a migration where I
· Add a new nullable column
On Wed, Aug 7, 2019 at 3:34 PM Daniel Fink (PDF) wrote:
> My current idea is to lock both tables completely from access (the queried
> and the updated one) so that postgresql does not have to ensure isolation for
> concurrent queries by keeping a copy of each row.
I'm not sure that locking
> On Aug 7, 2019, at 7:34 AM, Daniel Fink (PDF) wrote:
>
> Hi all,
>
> I have a migration where I
> · Add a new nullable column to a table
> · update almost every row in this big table (8 million rows) from
> another table where I set this new column
>
> I have also a
Hi all,
I have a migration where I
· Add a new nullable column to a table
· update almost every row in this big table (8 million rows) from
another table where I set this new column
I have also a replication setup running.
The database has a size of around 20GB.
While the
