Re: Is stats update during COPY IN really a good idea?

> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > People are using COPY into the same table at the same time? 
> 
> Yes --- we had a message from someone who was doing that (and running
> into unrelated performance issues) just last week.

OK.

> > My vote is to update pg_class.  The VACUUM takes much more time than the
> > update, and we are only updating the pg_class row, right?
> 
> What?  What does VACUUM have to do with this?

You have to VACUUM to get pg_class updated after COPY, right?

> The reason this is a significant issue is that the first COPY could be
> inside a transaction, in which case the lock will persist until that
> transaction commits, which could be awhile.

Oh, I see.  Can we disable the pg_class update if we are in a
multi-statement transaction?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026