| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | RekGRpth <rekgrpth(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17303: statement_timeout does not work always |
| Date: | 2021-11-29 13:54:07 |
| Message-ID: | CAKFQuwbNVi6gtW3EEafCn7Ainy+5cXV=x2a5tfnnMiEkB142Ug@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Nov 29, 2021 at 1:50 AM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> Why statement_timeout does not work always in postgres 10.19?
>
Due to questions like yours it was decided the behavior of "psql -c" needed
to be changed. But it is good software practice to not change such
behavior on a minor release. Thus the current version of 10 has the old
behavior and the current version of 14 has the improved behavior (I don't
recall when exactly it changed). This is not a bug, it is just how
softwares changes over time.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Poot, Bas (B.J.) | 2021-11-29 14:08:36 | subselect removes rows |
| Previous Message | Juan José Santamaría Flecha | 2021-11-29 07:53:28 | Re: BUG #17288: PSQL bug with COPY command (Windows) |