Re: Implement UNLOGGED clause for COPY FROM

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "osumi(dot)takamichi(at)fujitsu(dot)com" <osumi(dot)takamichi(at)fujitsu(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Implement UNLOGGED clause for COPY FROM
Date: 2020-07-09 05:07:46
Message-ID: CAKFQuwbqDGVt6opR8sX=+RmBHpdkE4D2Z-HJH1brgEyq57RqLA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday, July 8, 2020, osumi(dot)takamichi(at)fujitsu(dot)com <
osumi(dot)takamichi(at)fujitsu(dot)com> wrote:
>
> 5. Sync the data to disk by performing checkpoint.
>

This step seems to invalidate the idea outright. The checkpoint command is
superuser only and isn’t table specific. This seems to require both those
things to be changed.

Aside from that, though, how does this improve upon the existing capability
to copy into an unlogged temporary table?

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2020-07-09 05:18:35 Re: pg_resetwal --next-transaction-id may cause database failed to restart.
Previous Message Alvaro Herrera 2020-07-09 04:54:02 Re: pgsql-hackers archive broken?