| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Subject: | Re: Allow workers to override datallowconn |
| Date: | 2018-02-22 20:32:38 |
| Message-ID: | 20180222203238.bpbh2ygkhyhglwg6@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2018-02-22 15:24:50 -0500, Tom Lane wrote:
> You could possibly make it work with more aggressive refactoring, but
> I remain of the opinion that this is a fundamentally bad idea anyhow.
> A GUC of this kind is just ripe for abuse, and I don't think it's solving
> any problem we really need solved.
Oh, and I actually find this a thing that I needed a couple times
before. Databases used as templates are occasionally useful. To fill
their contents one usually wants to connect to them occasionally, but
most of the time connections ought to not be allowed so creating a
database with them as a template actually works. It's solvable via
other means, but not conveniently.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2018-02-22 20:52:10 | Re: Hash Joins vs. Bloom Filters / take 2 |
| Previous Message | Andres Freund | 2018-02-22 20:30:26 | Re: Allow workers to override datallowconn |