> -Original Message-
> From: Vik Fearing [mailto:vik.fear...@2ndquadrant.com]
> Sent: Friday, March 02, 2018 20:56
> To: l...@laurent-hasson.com; pgsql-performance@lists.postgresql.org
> Cc: Stephen Frost
> Subject: Re: Updating large tables without dead tuples
>
On 02/24/2018 12:27 AM, l...@laurent-hasson.com wrote:
> Hello
>
>
>
> I work with a large and wide table (about 300 million rows, about 50
> columns), and from time to time, we get business requirements to make
> some modifications. But sometimes, it’s just some plain mistake. This
> has happe
Greetings,
* l...@laurent-hasson.com (l...@laurent-hasson.com) wrote:
> > * l...@laurent-hasson.com (l...@laurent-hasson.com) wrote:
> > > This was done during a maintenance window, and that table is read-only
> > except when we ETL data to it on a weekly basis, and so I was just wondering
> > why
> -Original Message-
> From: Stephen Frost [mailto:sfr...@snowman.net]
> Sent: Friday, February 23, 2018 19:10
> To: l...@laurent-hasson.com
> Cc: pgsql-performance@lists.postgresql.org
> Subject: Re: Updating large tables without dead tuples
>
> Greetings,
>
Greetings,
* l...@laurent-hasson.com (l...@laurent-hasson.com) wrote:
> This was done during a maintenance window, and that table is read-only except
> when we ETL data to it on a weekly basis, and so I was just wondering why I
> should pay the "bloat" penalty for this type of transaction. Is th
