| From: | Shawn <shamccoy(at)amazon(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: An unkillable connection caused replication delay on my replica |
| Date: | 2016-06-29 14:56:35 |
| Message-ID: | 1467212195613-5909883.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Unfortunately...no. I have been trying to repro this scenario. Is there a
specific way to make a Python connection where this is possible?
My end game, if this is not something that can be fixed on the Postgres
side, is to come up with a way to automatically cause the connection to drop
(iptables, something else...etc).
--
View this message in context: http://postgresql.nabble.com/An-unkillable-connection-caused-replication-delay-on-my-replica-tp5909767p5909883.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Khandekar | 2016-06-29 15:00:21 | Re: asynchronous and vectorized execution |
| Previous Message | Tom Lane | 2016-06-29 14:48:09 | Re: Strange behavior of some volatile function like random(), nextval() |