| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mark Cave-Ayland" <m(dot)cave-ayland(at)webbased(dot)co(dot)uk> |
| Cc: | "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers-win32(at)postgresql(dot)org, "'PostgreSQL-patches'" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] GUC variables invisible to contrib/ modules |
| Date: | 2004-08-17 15:18:29 |
| Message-ID: | 4644.1092755909@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 pgsql-patches |
"Mark Cave-Ayland" <m(dot)cave-ayland(at)webbased(dot)co(dot)uk> writes:
> So I guess I was looking more for clarification that this was the
> "official" way to access GUC information?
It isn't, and isn't likely to become so, at least not for C code.
We generally think of the C code as being at a lower level than SQL.
If we rename a global variable that underlies a GUC variable, it's
probably because we *want* to break any C code that references it
--- perhaps the semantics are changing, or something like that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2004-08-17 15:30:03 | Re: tablespace and sequences? |
| Previous Message | Bruce Momjian | 2004-08-17 15:17:26 | Re: tablespace and sequences? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-08-17 15:22:01 | Re: [BUGS] 8.0.0beta1: -lpthread missing |
| Previous Message | Bruce Momjian | 2004-08-17 15:15:36 | Re: [PATCHES] GUC variables invisible to contrib/ |