| From: | Michał Hankiewicz <hankiewicz(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #7600: Database crash with data corruption |
| Date: | 2012-10-15 13:56:43 |
| Message-ID: | CAMpaLZqdWaSj5kKAEmR10GC1UVmODgCyv4VrhUqLbWnHM=yAqQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Oct 15, 2012 at 3:31 PM, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> wrote:
>
> OK, that sounds more like a problem. It wasn't clear from your original
> post that it was replaying used sequence values.
>
> SIGINT should normally just terminate the statement, eg:
>
> regress=# SELECT pg_sleep(100);
> ERROR: canceling statement due to user request
>
> so I agree that something isn't right here.
>
> Is this something you've been able to reproduce? Or is it a one-off
> incident so far?
>
> --
> Craig Ringer
>
>
It is just one-off incident. We have increased sequences values and since
friday everything is running fine.
We haven't tried to reproduce this situation.
Michał Hankiewicz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2012-10-15 14:27:56 | Re: BUG #7534: walreceiver takes long time to detect n/w breakdown |
| Previous Message | Craig Ringer | 2012-10-15 13:31:26 | Re: BUG #7600: Database crash with data corruption |