| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: FWD: Re: Updated backslash consistency patch |
| Date: | 2009-01-16 03:58:12 |
| Message-ID: | 27467.1232078292@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> As I mentioned in my other email, this is mainly for PostGIS, but it can
> certainly apply to other modules. Is this what we would recommend as an
> approach for these kinds of modules? I feel like that would give
> -hackers, or perhaps the PostGIS people, some heartburn, but maybe I'm
> wrong?
If you have an idle evening you might want to peruse all the past
threads about developing better support for modules. This is clearly
an area where we need to improve, and it's also clear that no quick
hack is going to make it significantly better (in fact, it might make
things worse by creating extra compatibility issues when we do get
around to implementing a real solution).
The main argument against sticking stuff into pg_catalog is that
pg_dump will think it's a built-in and not dump it. In some respects
that could be a plus, but for the most part it's a headache.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-01-16 04:00:39 | Re: FWD: Re: Updated backslash consistency patch |
| Previous Message | Stephen Frost | 2009-01-16 03:50:23 | Re: FWD: Re: Updated backslash consistency patch |