Re: BUG #15000: Cache lookup failure

From: Thomas Kellerer <thomas(at)kellerer(dot)eu>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15000: Cache lookup failure
Date: 2018-01-08 15:49:20
Message-ID: 23e16357-4c85-48cf-799a-30aa5ab18405@kellerer.eu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane schrieb am 08.01.2018 um 16:35:
> OK. The explanation then presumably is that something is dropping that
> table concurrently with the pg_dump run. It remains unclear to me why
> pg_dump is failing to protect itself against such a drop, but before we
> can figure that out, we need to be able to reproduce the situation.
>
>
> Can you identify anything that would be dropping tables concurrently
> with this script?

I feel ashamed :(

There was a left over pipe symbol in the script that we didn't see:

pg_dump --table=l10n --table=l10n_value --clean ${db_stag} |
psql --single-transaction --dbname=${db_prod} --file=${backup_stag}

So pg_dump pipes a script with DROP statement into psql, which then
runs essentially the same script again which was created in a previous step (also with --clean)

Seeing my (stupid) mistake, I am not sure if this is supposed to work or not...

Thomas

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2018-01-08 16:04:56 Re: BUG #15000: Cache lookup failure
Previous Message Tom Lane 2018-01-08 15:35:11 Re: BUG #15000: Cache lookup failure