Re: BUG #15000: Cache lookup failure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Kellerer <thomas(at)kellerer(dot)eu>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15000: Cache lookup failure
Date: 2018-01-08 16:04:56
Message-ID: 32171.1515427496@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thomas Kellerer <thomas(at)kellerer(dot)eu> writes:
> 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?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Todd A. Cook 2018-01-08 17:09:56 Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop
Previous Message Thomas Kellerer 2018-01-08 15:49:20 Re: BUG #15000: Cache lookup failure