| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | hankiewicz(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #7600: Database crash with data corruption |
| Date: | 2012-10-12 15:05:43 |
| Message-ID: | 23056.1350054343@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
hankiewicz(at)gmail(dot)com writes:
> The list of steps to reproduce bug:
> 1) Create two database on single server instance (production and sandbox)
> 2) On production perform normal operations (we use Trac with over 50 active
> users)
> 3) on the sandbox database start explain plan of query
> 4) while explain plan is executing drop sandbox database
> 5) after recovery was completed we have discovered that sequences on
> production database had wrong values
It's normal for sequences to be advanced by a few counts (up to 32)
after a database crash. You seem to have done a "kill -9" on the
backend that was running the EXPLAIN, which would count as a crash.
So I don't see any bug here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-10-12 21:24:31 | Re: BUG #7598: Loss of view performance after dump/restore of the view definition |
| Previous Message | Dave Page | 2012-10-12 14:35:05 | Re: BUG #7601: Installation of PostGresql at c:\Progam files folder does not create right permission on data folder |