From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Steve Baldwin <steve(dot)baldwin(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Transaction prevention |
Date: | 2020-07-30 01:10:13 |
Message-ID: | 1346557.1596071413@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Steve Baldwin <steve(dot)baldwin(at)gmail(dot)com> writes:
> Thanks Tom. The idle_in_transaction_session_timeout could work well, but it
> seems to be just a default that can be overridden by a user post-login (or
> am I missing something?).
It is that, but if you have an actively malicious user then you need to
keep them from issuing SQL directly at all. There are far too many ways
to cause effective denial-of-service, eg a single query that runs
"forever".
> I'm thinking of setting lock_timeout as part of
> the migration process so it will fail if it is unable to obtain a lock in a
> 'reasonable' amount of time. I wonder what other folks do?
If you'd rather fail the migration process, sure.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Argha Deep Ghoshal | 2020-07-30 07:56:18 | PSQLException: An I/O error occurred while sending to the backend. |
Previous Message | Steve Baldwin | 2020-07-30 00:50:33 | Re: Transaction prevention |