From: | Michael Nolan <htfoot(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Darren Duncan <darren(at)darrenduncan(dot)net>, Jeff Davis <pgsql(at)j-davis(dot)com>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>, mike beeper <mbeeper(at)hotmail(dot)com>, pgsql-general(at)postgresql(dot)org, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Creating temp tables inside read only transactions |
Date: | 2011-07-11 04:01:13 |
Message-ID: | CAOzAquJiDtVcybmkFZ1GhwABdU3r8pWWKmeztEs58Di33jwnjQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Fri, Jul 8, 2011 at 10:27 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> But if that's what you want, just don't put your data in different
> databases in the first place. That's what schemas are for.
>
Sadly, DBAs don't always have the ability to put all their data in one
database, even if that is what schemas are for.
The ability to do cross-database (most likely cross-server as well) queries
would address a lot of real-world problems.
-
Mike Nolan
nolan(at)tssi(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2011-07-11 04:16:10 | Re: [HACKERS] Creating temp tables inside read only transactions |
Previous Message | Tim Uckun | 2011-07-10 23:58:33 | Unexpected results when joining on date fields |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-07-11 04:11:02 | Re: per-column generic option |
Previous Message | Bruce Momjian | 2011-07-11 03:47:36 | Re: Need help understanding pg_locks |