Re: [HACKERS] One-shot expanded output in psql using \G
От | Stephen Frost |
---|---|
Тема | Re: [HACKERS] One-shot expanded output in psql using \G |
Дата | |
Msg-id | 20170127153116.GF9812@tamriel.snowman.net обсуждение исходный текст |
Ответ на | Re: [HACKERS] One-shot expanded output in psql using \G (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] One-shot expanded output in psql using \G
Re: [HACKERS] One-shot expanded output in psql using \G |
Список | pgsql-hackers |
* Alvaro Herrera (alvherre@2ndquadrant.com) wrote: > D'Arcy Cain wrote: > > > I am a pretty heavy user of psql but I don't think that that would be so > > helpful. I assume you mean a new option, let's call it "\X" the causes the > > next query to be expanded. I type "\X" then a query. I realize that I made > > a mistake and have to redo the query so I have to type "\X" again. If I > > forget then I have to run the query yet again. > > I think the suggestion is that \G replaces \g (which is the same thing > as the semicolon). So you would do this: > > SELECT * FROM table WHERE table_status = 1; % get a short list; normal output > SELECT * FROM table WHERE table_id = 123 \G % drill down to one ID Uh, I figured it was more like \g, which just re-runs the last query.. As in, you'd do: table pg_proc; % blargh, I can't read it like this \G % ahh, much nicer Thanks! Stephen
В списке pgsql-hackers по дате отправления: