| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Fernando Nasser <fnasser(at)redhat(dot)com> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Adds the parsing of a CREATE SCHEMA statement |
| Date: | 2002-03-01 16:26:39 |
| Message-ID: | 28696.1014999999@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
This self-modification of the CreateSchema statement makes my head hurt
... isn't there a cleaner way?
I would really like to see us move towards a processing pipeline in
which parse analysis, rewrite, planning, and execution steps each take
their input data structures as *read only*. I know it's not like that
today, but it needs to be so. If I were to enumerate the bugs we've had
in the past because of violations of that rule, I'd still be composing
this message at dinnertime. (And I still have a very long to-fix list
of kluges, workarounds, and memory leaks that are traceable to the lack
of read-only data structures.) I really really don't want to see any
new work introducing new violations of the rule.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-03-01 22:05:32 | Re: FW: [HACKERS] decode() function for PostgreSQL |
| Previous Message | Fernando Nasser | 2002-03-01 16:02:34 | Re: Allows for commands to be processed iteractively |