| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Alternative to \copy in psql modelled after \g |
| Date: | 2018-11-09 16:49:50 |
| Message-ID: | CAKFQuwZEk2hYm6i_RFjf8zejqJ91EEhaas=OAqZnYevyVtGbgg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 9, 2018 at 9:35 AM Daniel Verite <daniel(at)manitou-mail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-11-09 17:07:12 | Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |
| Previous Message | Jürgen Strobel | 2018-11-09 16:46:04 | BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |