| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Burgholzer, Robert (DEQ)" <Robert(dot)Burgholzer(at)deq(dot)virginia(dot)gov> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: catalog corruption causes |
| Date: | 2010-08-06 20:56:30 |
| Message-ID: | AANLkTin1Kx2wTYsdTgoYd4mrhrjY2r9KikJzR=YkvEDe@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, Aug 6, 2010 at 12:28 PM, Burgholzer, Robert (DEQ)
<Robert(dot)Burgholzer(at)deq(dot)virginia(dot)gov> wrote:
> I am trying to get my head around what causes catalog corruption. I
> have posted before with regard to recovering from corruptions (if that
> is what indeed happened to me), and was given much help.
>
> Does anyone know why a database catalog will get corrupted? As I
> mentioned previously, my db involves considerable use of temporary
> tables created by php-psql connections. Other than that, I don't know
> of too much that is "odd" about my use (misuse) of the database.
Note that it's also possible you've found some uncommon corner case
with pgsql code. If you have tested memory / cpu and can consistently
get corrupted catalogs by running a particular sequence of commands
against pgsql over and over then definitely report it and provide a
test case. Guidance on reporting problems here:
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomeh, Husam | 2010-08-07 00:19:06 | High-water Mark for number of sessions/connections reached in Postgres |
| Previous Message | Scott Marlowe | 2010-08-06 20:54:47 | Re: catalog corruption causes |