On Wed, 15 Mar 2006, Clark C. Evans wrote:
> On Tue, Mar 14, 2006 at 11:11:29PM -0800, Stephan Szabo wrote:
> | When we're allowing other order access, immediately reorder the
> | constraint information to match the primary key order.
>
> Let me try to parrot. In PostgreSQL, the pairing informati
On Tue, Mar 14, 2006 at 11:11:29PM -0800, Stephan Szabo wrote:
| When we're allowing other order access, immediately reorder the
| constraint information to match the primary key order.
Let me try to parrot. In PostgreSQL, the pairing information between
the foreign-key and unique-key constraint
On Wed, 15 Mar 2006, Clark C. Evans wrote:
> On Tue, Mar 14, 2006 at 10:01:16PM -0800, Stephan Szabo wrote:
> | The point is that because rows in a table don't have order (unless
> | information_schema has special rules) the two constraints above seem to
> | look the same to me in their represent
On Tue, Mar 14, 2006 at 10:01:16PM -0800, Stephan Szabo wrote:
| The point is that because rows in a table don't have order (unless
| information_schema has special rules) the two constraints above seem to
| look the same to me in their representation in
| information_schema.constraint_column_usage
On Tue, 14 Mar 2006, Stephan Szabo wrote:
> We need to offer this for spec complience reasons, but I don't think it
> actually fixes the problem you would have with information_schema.
Which of course is wrong, as i figured out when the discussion came up the
first time and forgot when I came to
On Wed, 15 Mar 2006, Clark C. Evans wrote:
> On Tue, Mar 14, 2006 at 08:14:12PM -0800, Stephan Szabo wrote:
> | > CREATE TABLE x (y text, z text, PRIMARY KEY(y,z));
> | > CREATE TABLE a (b text, c text);
> | > ALTER TABLE a ADD FOREIGN KEY (b, c) REFERENCES x(z, y);
> ...
> | > I asser
I want to write a function to expose the content of WAL Files as streams,
and then send to somewhere else, record by record.
Could you tell me something about the internal structure of the WAL Files?
Thank you very much!
---(end of broadcast)---
On Tue, Mar 14, 2006 at 08:14:12PM -0800, Stephan Szabo wrote:
| > CREATE TABLE x (y text, z text, PRIMARY KEY(y,z));
| > CREATE TABLE a (b text, c text);
| > ALTER TABLE a ADD FOREIGN KEY (b, c) REFERENCES x(z, y);
...
| > I assert the problem here is that the FOREIGN KEY constraint
|
[Resurrecting an old thread]
On Sat, 25 Feb 2006, Clark C. Evans wrote:
> On Sat, Feb 25, 2006 at 12:51:51PM -0800, Stephan Szabo wrote:
> | > > * for foreign-key and check constraints, the default names
> | > > are $1, $2, etc.; it would be great if they were "upgraded"
> | > > to use
On Tue, Mar 14, 2006 at 08:50:22AM +, Simon Riggs wrote:
> Is the issue that the log volume is too high? We might be able to look
> at ways to reduce/compress the log volume for duration/statement
> logging.
ISTM that for performance analysis there's probably a better alternative
than just dum
On Tue, Mar 14, 2006 at 02:12:39PM -0500, Jonah H. Harris wrote:
> On 3/14/06, Jim C. Nasby <[EMAIL PROTECTED]> wrote:
> >
> > Setting up Slony might be another option; you'd essentially be following
> > the procedure used to speed up a PostgreSQL upgrade that would normally
> > require a dump/relo
On 3/14/06, Jim C. Nasby <[EMAIL PROTECTED]> wrote:
Setting up Slony might be another option; you'd essentially be followingthe procedure used to speed up a PostgreSQL upgrade that would normallyrequire a dump/reload.
If you need to do this on a continuing basis, Slony is the best way to
go. If it
On Mon, Mar 13, 2006 at 01:36:28PM -0500, Jonah H. Harris wrote:
> What could be done in order to fix it? Is there any kind of application to
> > translate it or the only solution was to "pg_dumpall" and "pg_restore" the
> > cluster?
> >
>
> Yes, dump and restore is the best way to go.
Setting up
On Sat, Mar 11, 2006 at 10:21:43PM +0200, Hannu Krosing wrote:
> > table partitioning, I keep wondering whether it would be possible
> > to move rows near the end of the table to the beginning in one, non-
> > locking
> > phase (vacuum to populate FSM with free space near beginning of table,
> > t
"Peter Zeltins" <[EMAIL PROTECTED]> writes:
> On my laptop (WinXP, PG 8.1.1, ActivePerl 5.8.7) it eats up around
> 1M/second - ran it for ~10 minutes, and it was barely 10% through it's
> calculations. On our test server (FreeBSD 5.4, PG 8.1.2, Perl 5.8.7) it
> happens a bit faster, 400MB are co
Simon,
On 3/14/06, Simon Riggs <[EMAIL PROTECTED]> wrote:
> Thanks very much for writing pgFouine. We've been doing our best to
> support generation of useful logs for performance analysis, so please
> feel free to ask for anything you see a need for.
OK. Thanks. I should write something clear ab
On 3/14/06, Qingqing Zhou <[EMAIL PROTECTED]> wrote:
> I guess they should read as "2006" :-)
Sure. Will fix it this evening. Thanks.
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
""Guillaume Smet"" <[EMAIL PROTECTED]> wrote
>
> Here are some background information to explain our issue and request.
On a separate issue, seems in pgfouine homepage a typo is there for a while:
What's New
2005-02-11 - pgFouine 0.4.99 released ...
2005-01-10 - pgFouine 0.2.1 released ...
I gu
On Mon, 2006-03-13 at 17:38 +0900, ITAGAKI Takahiro wrote:
> Simon Riggs <[EMAIL PROTECTED]> wrote:
>
> > > "Zeugswetter Andreas DCP SD" <[EMAIL PROTECTED]> wrote:
> > > > Ok, we cannot reuse a dead tuple. Maybe we can reuse the space of a dead
> > > > tuple by reducing the tuple to it's header in
On Mon, 2006-03-13 at 23:40 +0100, Guillaume Smet wrote:
> Here are some background information to explain our issue and request.
> We are currently planning a migration from PostgreSQL 7.4 to
> PostgreSQL 8.1. We work on a medium sized database (2GB) with a rather
> important activity (12 million
Tom Lane wrote:
Worst case is we promote WITH to a fully reserved word. While I don't
normally care for doing that, it *is* a reserved word per SQL99, and
offhand I don't see likely scenarios for someone using "with" as a table
or column or function name. (Anyone know of a language in which "w
21 matches
Mail list logo
