| From: | Kev <kevinjamesfield(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: variables for tables and columns? |
| Date: | 2008-04-08 15:06:13 |
| Message-ID: | 863d674d-8236-462c-a182-9dcb48db1b8e@s13g2000prd.googlegroups.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Apr 8, 10:40 am, st(dot)(dot)(dot)(at)enterprisedb(dot)com (Gregory Stark) wrote:
> "Kev" <kevinjamesfi(dot)(dot)(dot)(at)gmail(dot)com> writes:
> > Would it be a lot of trouble to extend the ability that databases have
> > to store variables (add_missing_from, array_nulls, etc.) to tables and
> > columns, for use with user-defined variables?
>
> Not following what you're trying to say at all. Perhaps an example of how what
> you're thinking of would work would help?
Sorry, I mean whatever structure it is that lets you go into pgAdmin,
select a database, go to Properties, and hit the Variables tab. In
there you can set a bunch of per-database variables like
add_missing_from, search_path, etc.
I think these are just stored in pg_database.datconfig, no?
So what I would be proposing is adding that column to pg_attribute and
pg_class, I guess. But now that I put it that way it seems like that
would be a burden on some pretty key tables. Maybe it's not a very
good idea then.
Kev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-04-08 15:22:51 | Re: Kludge in pg_standby.c |
| Previous Message | Alvaro Herrera | 2008-04-08 15:05:27 | Snapshot memory management |