On 28/08/2018 21:51, Tom Lane wrote:
Hm, could I trouble you for a self-contained test case? I tried to
flesh it out as attached, but I'm not seeing any error with this.
So there must be some other moving part ...
regards, tom lane
Tom, the materialized view in quest
Tim Clarke writes:
> On 27/08/18 15:22, Tom Lane wrote:
>> That's not supposed to happen. Can you create a test case, by any chance?
> It wasn't the cross-tab/pivot, it was this materialized view:
Hm, could I trouble you for a self-contained test case? I tried to
flesh it out as attached, but
On 27/08/18 15:22, Tom Lane wrote:
>> That's not supposed to happen. Can you create a test case, by any chance?
>> Presumably, it's triggered by some database schema change you made since
>> the last successful dump.
>>
>> regards, tom lane
>>
It wasn't the cross-tab/pivot, i
On 27/08/18 15:22, Tom Lane wrote:
> Tim Clarke writes:
>> Last night for the first time our pg_dump backup threw this error for
>> the first time. Repeated runs this morning consistently throw it too.
> That's not supposed to happen. Can you create a test case, by any chance?
> Presumably, it's
Tim Clarke writes:
> Last night for the first time our pg_dump backup threw this error for
> the first time. Repeated runs this morning consistently throw it too.
That's not supposed to happen. Can you create a test case, by any chance?
Presumably, it's triggered by some database schema change y
On 08/27/2018 03:59 AM, Tim Clarke wrote:
Last night for the first time our pg_dump backup threw this error for
the first time. Repeated runs this morning consistently throw it too. I
can see the error in the Postgres source
https://doxygen.postgresql.org/pg__backup__archiver_8c_source.html but
