Re: Alternative to \copy in psql modelled after \g - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Alternative to \copy in psql modelled after \g
Date
Msg-id CAKFQuwZEk2hYm6i_RFjf8zejqJ91EEhaas=OAqZnYevyVtGbgg@mail.gmail.com
Whole thread Raw
In response to Re: Alternative to \copy in psql modelled after \g  ("Daniel Verite" <daniel@manitou-mail.org>)
Responses Re: Alternative to \copy in psql modelled after \g  ("Daniel Verite" <daniel@manitou-mail.org>)
List pgsql-hackers
On Fri, Nov 9, 2018 at 9:35 AM Daniel Verite <daniel@manitou-mail.org> wrote:
> If for instance psql received a notification between the two \o it would
> end up in the file, which it wouldn't with \copyto.
> The same is true for  SELECT... \g file as opposed to \o file

Is that something we could change instead of adding a new command?
POLA, for me at least, would be for \g [filename] to do exactly what
you are describing with the \copyto feature. That is doesn't and there
haven't been complaints I would chalk up to notices and command
responses not being prevalent in situations where people would use \g
[filename] or paired \o [filename].

David J.


pgsql-hackers by date:

Previous
From: Jürgen Strobel
Date:
Subject: BUG #15212: Default values in partition tables don't work as expectedand allow NOT NULL violation
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #15212: Default values in partition tables don't work asexpected and allow NOT NULL violation