Re: Confusing behavior of psql's \e - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Confusing behavior of psql's \e
Date
Msg-id 58832.1617486237@sss.pgh.pa.us
Whole thread Raw
In response to Confusing behavior of psql's \e  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Confusing behavior of psql's \e
List pgsql-hackers
Laurenz Albe <laurenz.albe@cybertec.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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: "Daniel Verite"
Date:
Subject: Re: insensitive collations
Next
From: Andres Freund
Date:
Subject: Allowing dsm allocations in single user mode