| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Rajeev rastogi <rajeev(dot)rastogi(at)huawei(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: datistemplate of pg_database does not behave as per description in documentation |
| Date: | 2014-03-27 11:24:35 |
| Message-ID: | 20140327112435.GG4582@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Magnus Hagander (magnus(at)hagander(dot)net) wrote:
> However, that also raises a third option. We could just drop the idea if
> datistemplate completely, and remove the column. Since clearly it's not
> actually doing anything, and people seem to have been happy with that for a
> while, why do we need it in the first place?
It's a bit of extra meta-data which can be nice to have (I know we use
that field for our own purposes..). On the flip side, I've never liked
that you have to update pg_database to change it, so perhaps we should
get rid of it and remove that temptation.
The other field we regularly update in pg_database is datallowconn...
Would love to see that as an actual ALTER DATABASE command instead...
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-03-27 11:45:52 | Re: datistemplate of pg_database does not behave as per description in documentation |
| Previous Message | Christoph Berg | 2014-03-27 09:02:20 | Re: Useless "Replica Identity: NOTHING" noise from psql \d |