| From: | Christoph Berg <christoph(dot)berg(at)credativ(dot)de> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #9198: psql -c 'SET; ...' not working |
| Date: | 2014-02-12 13:09:22 |
| Message-ID: | 20140212130922.GC4409@msgid.df7cb.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Re: To pgsql-bugs(at)postgresql(dot)org 2014-02-12 <20140212125626(dot)2710(dot)94912(at)wrigleys(dot)postgresql(dot)org>
> time psql -c "SET statement_timeout = '3s'; SELECT pg_sleep(2)"
> ERROR: canceling statement due to statement timeout
> real 0m1.065s
>
> As witnessed by the time output, the timeout is the one from ALTER ROLE, not
> the new one. Seen on 9.2 and 9.3.
>
> The psql docs mention that -c is treated differently from stdin when
> multiple commands are executed, but that shouldn't include SET not getting
> into effect.
The same problem occurs with statement_timeout from postgresql.conf
and from PGOPTIONS.
Christoph
--
cb(at)df7cb(dot)de | http://www.df7cb.de/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-02-12 14:16:07 | Re: BUG #9190: Could not fsync file "pg_clog/0000": Bad file descriptor. |
| Previous Message | christoph.berg | 2014-02-12 12:56:26 | BUG #9198: psql -c 'SET; ...' not working |