| From: | Dmitry Tkach <dmitry(at)openratings(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3 |
| Date: | 2003-07-18 21:47:20 |
| Message-ID: | 3F186AE8.2030504@openratings.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
>Proves nothing, since ANALYZE only touches a random sample of the rows.
>
>
Ok, I understand... Thanks.
>If you get that behavior with VACUUM, or a full-table SELECT (say,
>"SELECT count(*) FROM foo"), then it'd be interesting.
>
>
I never got it with select - only with vacuum and/or analyze...
I you suggesting it should/could happen with select, or was that just
meant to be an example of a full table scan?
I just did select count (*) from that table, and it worked...
>What range of file names do you actually have in pg_clog/, anyway?
>
>
>
Well ... *today* there seem to be files between 0000 and 00EC
Is that range supposed to stay the same or does it vary?
... because that problem I had happened yesterday, and I have restarted
the server since then...
Thanks!
Dima
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maksim Likharev | 2003-07-18 21:50:58 | Re: ODBC query problem AGAIN |
| Previous Message | Luis Magaña | 2003-07-18 21:43:00 | ODBC query problem AGAIN |