Re: [HACKERS] One-shot expanded output in psql using \gx
От | Noah Misch |
---|---|
Тема | Re: [HACKERS] One-shot expanded output in psql using \gx |
Дата | |
Msg-id | 20170817022441.GA3963697@rfd.leadboat.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] One-shot expanded output in psql using \gx (Tobias Bussmann <t.bussmann@gmx.net>) |
Ответы |
Re: [HACKERS] One-shot expanded output in psql using \gx
Re: [HACKERS] One-shot expanded output in psql using \gx Re: [HACKERS] One-shot expanded output in psql using \gx Re: [HACKERS] One-shot expanded output in psql using \gx |
Список | pgsql-hackers |
On Tue, Aug 15, 2017 at 10:24:34PM +0200, Tobias Bussmann wrote: > I've tested the new \gx against 10beta and current git HEAD. Actually one of my favourite features of PostgreSQL 10! Howeverin my environment it was behaving strangely. After some debugging I found that \gx does not work if you have \setFETCH_COUNT n before. Please find attached a patch that fixes this incl. new regression test. [Action required within three days. This is a generic notification.] The above-described topic is currently a PostgreSQL 10 open item. Stephen, since you committed the patch believed to have created it, you own this open item. If some other commit is more relevant or if this does not belong as a v10 open item, please let us know. Otherwise, please observe the policy on open item ownership[1] and send a status update within three calendar days of this message. Include a date for your subsequent status update. Testers may discover new open items at any time, and I want to plan to get them all fixed well in advance of shipping v10. Consequently, I will appreciate your efforts toward speedy resolution. Thanks. [1] https://www.postgresql.org/message-id/20170404140717.GA2675809%40tornado.leadboat.com
В списке pgsql-hackers по дате отправления: