Re: Some pgq table rewrite incompatibility with logical decoding?

From: Jeremy Finzel <finzelj(at)gmail(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Some pgq table rewrite incompatibility with logical decoding?
Date: 2018-08-13 20:35:38
Message-ID: CAMa1XUhGRe+xvUrNAA0tAaPKFUhHz02eM83mBwOuvrMaa5K7wg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> I don't think that's true, for two reasons.
>
> Firstly, I don't think pgq updates catalogs directly, it simply truncates
> the queue tables when rotating them (which updates the relfilenode in
> pg_class, of course).
>
> Secondly, we're occasionally seeing this on systems that do not use pgq,
> but that do VACUUM FULL on custom "queue" tables. The symptoms are exactly
> the same ("ERROR: could not map filenode"). It's pretty damn rare and we
> don't have direct access to the systems, so investigation is difficult :-(
> Our current hypothesis is that it's somewhat related to subtransactions
> (because of triggers with exception blocks).
>
> Jeremy, are you able to reproduce the issue locally, using pgq? That would
> be very valuable.

We have tried but have been unable to reproduce it. If we do encounter it
again, we will plan on reporting back and seeing if we can do some deep
debugging.

Thanks,
Jeremy

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-08-13 21:23:22 Re: FailedAssertion on partprune
Previous Message Andrew Dunstan 2018-08-13 20:06:13 Re: libpq compression