| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Return of "can't paste into psql" issue |
| Date: | 2013-07-17 22:09:45 |
| Message-ID: | 51E71629.9040809@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/17/2013 12:20 PM, Andrew Dunstan wrote:
> What happens when you do this with "psql -n" ? My suspicion is it's the
> tab completion code, which I occasionally find it useful to disable this
> way - sadly one can't do that on the fly AFAIK.
Well, that works. But it disables readline, not just tab completion.
So it's nice that I don't have to *compile* without readline, but we
still have the issue that you can't paste large files and also have
readline.
So, an even more practical workaround (I've been using cat | psql), but
still a mysterious issue.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-07-17 22:17:35 | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
| Previous Message | Tom Lane | 2013-07-17 22:00:10 | Re: pg_memory_barrier() doesn't compile, let alone work, for me |