ew in question was dependent on another
materialized view (pointlessly). I've changed the underlying view to a
simple one and the problem message "archive items not in correct section
order" doesn't appear.
Simply nesting the materialized views doesn't cause the issue tho
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
2
LIMIT 1;
I've trimmed it down to even just one row and it still causes the
warning "pg_dump: [archiver] WARNING: archive items not in correct
section order"
It yields this data:
id | ytext | score
---+--+---
5 | 1996 | 0
--
Tim Clarke
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
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 I
can't find any specifics about the cause or
