From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Swaminathan Saikumar <swami(at)giveexam(dot)com> |
Cc: | Jorge Godoy <jgodoy(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, "Pettis, Barry" <Barry(dot)Pettis(at)atmel(dot)com>, Richard Huxton <dev(at)archonet(dot)com> |
Subject: | Re: Using tables in other PostGreSQL database |
Date: | 2008-03-28 07:30:00 |
Message-ID: | 20080328073000.GA9150@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Mar 27, 2008 at 10:29:37PM -0700, Swaminathan Saikumar wrote:
> 4. Why not provide that feature as a core feature, rather than an add-on? If
> the community really feels strongly about this, discourage this practice
> with a best-practices section, citing problems with examples, and
> workarounds. But why don't you provide this feature out of the box? After
> all, isn't widespread adoption of a high quality database like Postgres our
> overall goal?
Why do people read the word "add-on" in a negative way? All it means is
"not installed by default", which is probably a good thing since the
security implications are not trivial. Installation is just a
question of:
psql -f <dblink install script>
(assuming your admin didn't do a minimal install).
I'm unsure what "widespread adoption of postgres" has to do with any of
this though.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql-general-owner | 2008-03-28 07:31:34 | [pgsql-general] Daily digest v1.8035 (19 messages) |
Previous Message | Alain Roger | 2008-03-28 07:19:38 | Re: dunction issue |