| From: | Stuart Bishop <stuart(at)stuartbishop(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Subject: | Re: BUG #7546: Backups on hot standby cancelled despite hot_standby_feedback=on |
| Date: | 2012-09-19 14:02:52 |
| Message-ID: | CADmi=6NTPeRrBq-F=FxteGG_254aJ-bvaLHJ2d5O3erMfB=_ZQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Sep 19, 2012 at 6:56 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> You see buffer pin errors or you see the relation errors? Those arent the same.
> So if you see no buffer pin errors but relation lock ones in production your
> way to reproduce the issue isn't telling us very much ;)
On production I have seen both. I have only been able to confirm and
isolate the trigger of the buffer pin errors, and thus this bug
report. I mentioned the rarer relation lock error just in case it was
relevant.
> Do you have DDL logging enabled so you could investigate that?
>
> I really wonder why we don't bother logging the dbOid/relOid pair before we
> cancel transactions due to lock conflicts. That should make investigating such
> issues considerably easier...
I do have DDL logging enabled. I've waded through a two hour period on
the primary where the problem must have occurred and can see no DDL
except for the creation and dropping of temporary tables. My parser is
unfortunately grep and my eyeballs to filter out the noise.
--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | reinhard | 2012-09-19 15:59:45 | BUG #7559: syslogger doesn't close stdout and stderr |
| Previous Message | pathak.anurag | 2012-09-19 13:21:03 | BUG #7558: Postgres service not starting. |