Re: Confusing behavior of psql's \e

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jacob Champion <pchampion(at)vmware(dot)com>, "chap(at)anastigmatix(dot)net" <chap(at)anastigmatix(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Confusing behavior of psql's \e
Date: 2021-04-06 09:17:58
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Sat, 2021-04-03 at 17:43 -0400, Tom Lane wrote:
> Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> > Attached is version 6.
> Pushed with some mostly-cosmetic fiddling.
> One thing I changed that wasn't cosmetic is that as you had it,
> the behavior of "\e file" varied depending on whether the query
> buffer had been empty, which surely seems like a bad idea.
> I made it do discard_on_quit always in that case. I think there
> might be a case for discard_on_quit = false always, ie maybe
> the user wanted to load the file into the query buffer as-is.
> But it seems like a pretty weak case --- you'd be more likely
> to just use \i for that situation.

Thanks for that!

Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2021-04-06 09:37:48 Re: Allow batched insert during cross-partition updates
Previous Message Neil Chen 2021-04-06 08:56:36 Re: Key management with tests