On 03/05/2010 08:44 PM, John A. Sullivan III wrote:
On Fri, 2010-03-05 at 19:59 +, Daniel J. Summers wrote:
On 03/05/2010 07:44 PM, John A. Sullivan III wrote:
I'm trying to avoid making a thousand call like
select user1.session_id from user1.sessions;
when I could do it in a si
On Fri, 2010-03-05 at 14:13 -0800, Bob Lunney wrote:
>
> --- On Fri, 3/5/10, John A. Sullivan III
> wrote:
>
> > From: John A. Sullivan III
> > Subject: [ADMIN] Querying the same column and table across schemas
> > To: pgsql-admin@postgresql.org
> > Date: Friday, March 5, 2010, 2:44 PM
> > Hel
--- On Fri, 3/5/10, John A. Sullivan III wrote:
> From: John A. Sullivan III
> Subject: [ADMIN] Querying the same column and table across schemas
> To: pgsql-admin@postgresql.org
> Date: Friday, March 5, 2010, 2:44 PM
> Hello, all. I'm working on a
> project using the X2Go terminal server
> p
On Fri, 2010-03-05 at 19:59 +, Daniel J. Summers wrote:
> On 03/05/2010 07:44 PM, John A. Sullivan III wrote:
> > I'm trying to avoid making a thousand call like
> >
> > select user1.session_id from user1.sessions;
> >
> > when I could do it in a single query especially since the database is
>
On 03/05/2010 07:44 PM, John A. Sullivan III wrote:
I'm trying to avoid making a thousand call like
select user1.session_id from user1.sessions;
when I could do it in a single query especially since the database is
remote and secured with SSL.
CREATE VIEW all_sessions AS
SELECT user1.sessi
Hello, all. I'm working on a project using the X2Go terminal server
project (www.x2go.org). They record session data in a postgresql
database. Our environment is a little more secure than typical and we
do not want it possible for one user to see another's session data. We
thus have divided the
You may want to try Bucardo ... By performance, are you referring to latency?
If so, bandwidth between sites typically is the factor with latency in any
replication solution.
http://bucardo.org/
-Original Message-
From: pgsql-sql-ow...@postgresql.org [mailto:pgsql-sql-ow...@postgres
On Fri, 2010-03-05 at 09:20 +0100, Iñigo Martinez Lasala wrote:
> For example, if you use functions or sentences that make use of
> timestamp, random, etc it won't be possible to use pg_pool since each
> node will have a different value.
> If not, it could probably work for you.
FWIW, timestamps
Until now, the only solution that has worked for us is pg_pool, but is
not always possible to use it.
For example, if you use functions or sentences that make use of
timestamp, random, etc it won't be possible to use pg_pool since each
node will have a different value.
If not, it could probably wor
