From: | Christoph Berg <myon(at)debian(dot)org> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: psql: Allow editing query results with \gedit |
Date: | 2024-01-23 10:38:22 |
Message-ID: | Za-XHowF7YjkIuRd@msg.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Re: Pavel Stehule
> It looks great for simple queries, but if somebody uses it like SELECT *
> FROM pg_proc \gedit
What's wrong with that? If the pager can handle the amount of data,
the editor can do that as well. (If not, the fix is to just not run
the command, and not blame the feature.)
> I almost sure so \gedit is wrong name for this feature.
I'm open for suggestions.
> Can be nice if we are able:
>
> a) export data set in some readable format
>
> b) be possible to use more command in pipes
>
> some like
>
> select start, call, qrg, name from log where cty = 'CE9' order by start
> \gpipexec(tsv) mypipe | bash update_pattern.sh > tmpfile; vi tmpfile; cat
> tmpfile > mypipe
Well yeah, that's still a lot of typing.
> I understand your motivation well, but I don't like your proposal because
> too many different things are pushed to one feature, and it is designed for
> a single purpose.
It's one feature for one purpose. And the patch isn't *that* huge. Did
I make the mistake of adding documentation, extra command options, and
tab completion in v1?
Christoph
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Lakhin | 2024-01-23 11:00:01 | Re: BUG: Former primary node might stuck when started as a standby |
Previous Message | Heikki Linnakangas | 2024-01-23 10:33:50 | Re: make BuiltinTrancheNames less ugly |