| From: | Tobias Bussmann <t(dot)bussmann(at)gmx(dot)net> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Christoph Berg <christoph(dot)berg(at)credativ(dot)de>, Daniel Verite <daniel(at)manitou-mail(dot)org>, David Fetter <david(at)fetter(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: One-shot expanded output in psql using \gx |
| Date: | 2017-08-15 20:24:34 |
| Message-ID: | CB7A53AA-5645-4BDD-AB07-4D22CD9D8FF1@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I've tested the new \gx against 10beta and current git HEAD. Actually one of my favourite features of PostgreSQL 10! However in my environment it was behaving strangely. After some debugging I found that \gx does not work if you have \set FETCH_COUNT n before. Please find attached a patch that fixes this incl. new regression test.
Best regards,
Tobias
| Attachment | Content-Type | Size |
|---|---|---|
| psql_gx_fetch_count_v1.patch | application/octet-stream | 1.7 KB |
| unknown_filename | text/plain | 3 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-08-15 20:25:07 | Re: increasing the default WAL segment size |
| Previous Message | Peter Eisentraut | 2017-08-15 20:23:35 | Re: A suspicious code in pgoutput_startup(). |