> -Original Message-
> From: Vik Fearing [mailto:[email protected]]
> Sent: Friday, March 02, 2018 20:56
> To: [email protected]; [email protected]
> Cc: Stephen Frost
> Subject: Re: Updating large tables without dead tuples
>
On 02/24/2018 12:27 AM, [email protected] 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,
* [email protected] ([email protected]) wrote:
> > * [email protected] ([email protected]) 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:[email protected]]
> Sent: Friday, February 23, 2018 19:10
> To: [email protected]
> Cc: [email protected]
> Subject: Re: Updating large tables without dead tuples
>
> Greetings,
>
Greetings,
* [email protected] ([email protected]) 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
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 happened to us a few
weeks ago where someone made a mistake and we had to up
