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 21:16:57
Message-ID: f87ba316-781b-52e2-d7d0-5bc77c26b24b@kellerer.eu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane schrieb am 08.01.2018 um 17:04:
>> 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)
>
> Hm, but if psql is restoring into a different database than pg_dump
> is dumping from, I don't see how they'd interact?

Yes, put psql is running the restore script (created with --clean) *twice*:
once because of the pipe and a second time because of the --file argument

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2018-01-09 04:27:20 Re: BUG #14941: Vacuum crashes
Previous Message Todd A. Cook 2018-01-08 17:09:56 Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop