Re: [GENERAL] select statement against pg_stats returns

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joe Conway <mail(at)joeconway(dot)com>, Shelby Cain <alyandon(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] select statement against pg_stats returns
Date: 2004-03-02 18:45:21
Message-ID: 200403021845.i22IjLO17409@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Christopher Kings-Lynne wrote:
> > Why? You can reconstruct it with a simple "ANALYZE" command. Dumping
> > and restoring would mean nailing down cross-version assumptions about
> > what it contains, which doesn't seem real forward-looking...
>
> I seem to recall that people like that kind of thing so that the dump is
> really the current state of the database.
>
> Also, I believe big db's like DB2 and Oracle do such a thing.
>
> I just recall it being discussed some time ago...

I have heard of dumping stats so you are sure your production db has the
same stats as your test database, but with ANALYZE so fast, and our
optimizer so good, I don't see a use case for us.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2004-03-02 18:57:40 Re: Moving from MySQL to PGSQL....some questions
Previous Message Knepper, Michelle 2004-03-02 18:11:58 Re: using the "copy from" command

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2004-03-02 20:08:22 Re: simple make check failures
Previous Message Chris Browne 2004-03-02 17:30:54 Re: User defined types -- Social Security number...