From: Mischa Sandberg <mischa.sandberg@telus.net>
To: pgsql-performance@postgresql.org
Subject: Re: Partitioning / Clustering
Date: Tue, 10 May 2005 19:19:13 -0700
Message-ID: <1115777953.42816ba1b4618@webmail.telus.net> (raw)
In-Reply-To: <20050510221554.GR31103@decibel.org>
References: <5F94B6EB-3925-4CD3-A67F-4310890B438A@advfn.com>
<4280C801.80603@arbash-meinel.com>
<DCFAEF09-885E-492C-A885-EEE405E7773F@advfn.com>
<1115762155.42812deb506d7@webmail.telus.net>
<20050510221554.GR31103@decibel.org>
Quoting "Jim C. Nasby" <decibel@decibel.org>:
> To the best of my knowledge no such work has been done. There is a
> project (who's name escapes me) that lets you run queries against a
> remote postgresql server from a postgresql connection to a different
> server, which could serve as the basis for what you're proposing.
Okay, if the following looks right to the powerthatbe, I'd like to start
a project. Here's the proposition:
"servername.dbname.schema.object" would change RangeVar, which would
affect much code. "dbname.schema.object" itself is not implemented in
8.0. So, simplicity dictates something like:
table pg_remote(schemaname text, connectby text, remoteschema text)
The pg_statistic info from a remote server cannot be cached in local
pg_statistic, without inventing pseudo reloids as well as a
pseudoschema. Probably cleaner to cache it somewhere else. I'm still
reading down the path that puts pg_statistic data where costsize can get
at it.
First step: find out whether one can link libpq.so to postmaster :-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mischa.sandberg@telus.net
Subject: Re: Partitioning / Clustering
In-Reply-To: <1115777953.42816ba1b4618@webmail.telus.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox