| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marti Raudsepp <marti(at)juffo(dot)org> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: dropdb --force |
| Date: | 2018-12-18 16:29:32 |
| Message-ID: | 8300.1545150572@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Marti Raudsepp <marti(at)juffo(dot)org> writes:
> I think Filip's approach of setting pg_database.datallowconn='false'
> is pretty clever to avoid the synchronization problem.
Some bull-in-a-china-shop has recently added logic that allows ignoring
datallowconn and connecting anyway, so I'm not sure that that'd provide
a production-quality solution. On the other hand, maybe we could revert
BGWORKER_BYPASS_ALLOWCONN.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-12-18 16:40:49 | Re: Should new partitions inherit their tablespace from their parent? |
| Previous Message | Justin Pryzby | 2018-12-18 16:24:39 | Re: psql exit status with multiple -c or -f |