>Please note this is only the case if wal_level = minimal. If replication
>(or PITR) is supported, that mode can't be used, because the data has to
>go into the WAL.
>Were you using wal_level = minimal?
Aha. No it was not minimal. For a second I thought PG is super smart. Oh well.
Thanks.
Hi,
On 2018-08-21 15:00:03 +, Ravi Krishna wrote:
> In a recent thread of mine I learned something very interesting. If a table
> is created and data is loaded via COPY FROM within the same transaction, then
> PG will be smart enough to not generate WAL logs because all it needs to do
> is
On 8/21/18 9:00 AM, Ravi Krishna wrote:
In a recent thread of mine I learned something very interesting. If a
table is created and data is loaded via COPY FROM within the same
transaction, then PG will be smart enough to not generate WAL logs
because all it needs to do is to track the status o
In a recent thread of mine I learned something very interesting. If a table is
created and data is loaded via COPY FROM within the same transaction, then PG
will be smart enough to not generate WAL logs because all it needs to do is to
track the status of the transaction and let the data load g
