forked from postgres/postgres
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Change Copyright from PostgreSQL, Inc to PostgreSQL Global Developmen…
…t Group.
- Loading branch information
Showing
617 changed files
with
1,408 additions
and
1,230 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,10 +4,6 @@ | |
b. palmer, [email protected] 1-17-2001 | ||
* Portions Copyright (c) 1996-2000, PostgreSQL, Inc | ||
* Portions Copyright (c) 1994, Regents of the University of California | ||
*/ | ||
|
||
#include <stdlib.h> | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,7 +2,7 @@ From [email protected] Sun Jan 23 13:31:03 2000 | |
Received: from renoir.op.net ([email protected] [207.29.195.4]) | ||
by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id NAA28482 | ||
for <[email protected]>; Sun, 23 Jan 2000 13:31:01 -0500 (EST) | ||
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.1 $) with ESMTP id NAA08409 for <[email protected]>; Sun, 23 Jan 2000 13:04:34 -0500 (EST) | ||
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.2 $) with ESMTP id NAA08409 for <[email protected]>; Sun, 23 Jan 2000 13:04:34 -0500 (EST) | ||
Received: from localhost (majordom@localhost) | ||
by hub.org (8.9.3/8.9.3) with SMTP id MAA65651; | ||
Sun, 23 Jan 2000 12:57:33 -0500 (EST) | ||
|
@@ -187,3 +187,67 @@ as part of Postgres unless these issues get addressed. | |
|
||
************ | ||
|
||
From [email protected] Wed Jan 24 14:20:02 2001 | ||
Received: from mail.postgresql.org (webmail.postgresql.org [216.126.85.28]) | ||
by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id OAA25380 | ||
for <[email protected]>; Wed, 24 Jan 2001 14:20:02 -0500 (EST) | ||
Received: from mail.postgresql.org (webmail.postgresql.org [216.126.85.28]) | ||
by mail.postgresql.org (8.11.1/8.11.1) with SMTP id f0OJHTq57982; | ||
Wed, 24 Jan 2001 14:17:29 -0500 (EST) | ||
(envelope-from [email protected]) | ||
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) | ||
by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0OIXnq49509 | ||
for <[email protected]>; Wed, 24 Jan 2001 13:33:49 -0500 (EST) | ||
(envelope-from [email protected]) | ||
Received: (from bright@localhost) | ||
by fw.wintelcom.net (8.10.0/8.10.0) id f0OIXgi14650; | ||
Wed, 24 Jan 2001 10:33:42 -0800 (PST) | ||
Date: Wed, 24 Jan 2001 10:33:42 -0800 | ||
From: Alfred Perlstein <[email protected]> | ||
To: Tom Lane <[email protected]> | ||
Cc: Bruce Momjian <[email protected]>, [email protected] | ||
Subject: Re: [HACKERS] Libpq async issues | ||
Message-ID: <[email protected]> | ||
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> | ||
Mime-Version: 1.0 | ||
Content-Type: text/plain; charset=us-ascii | ||
Content-Disposition: inline | ||
User-Agent: Mutt/1.2.5i | ||
In-Reply-To: <[email protected]>; from [email protected] on Wed, Jan 24, 2001 at 11:59:11AM -0500 | ||
Precedence: bulk | ||
Sender: [email protected] | ||
Status: OR | ||
|
||
* Tom Lane <[email protected]> [010124 10:27] wrote: | ||
> Alfred Perlstein <[email protected]> writes: | ||
> > * Bruce Momjian <[email protected]> [010124 07:58] wrote: | ||
> >> I have added this email to TODO.detail and a mention in the TODO list. | ||
> | ||
> > The bug mentioned here is long gone, | ||
> | ||
> Au contraire, the misdesign is still there. The nonblock-mode code | ||
> will *never* be reliable under stress until something is done about | ||
> that, and that means fairly extensive code and API changes. | ||
|
||
The "bug" is the one mentioned in the first paragraph of the email | ||
where I broke _blocking_ connections for a short period. | ||
|
||
I still need to fix async connections for myself (and of course | ||
contribute it back), but I just haven't had the time. If anyone | ||
else wants it fixed earlier they can wait for me to do it, do it | ||
themself, contract me to do it or hope someone else comes along | ||
to fix it. | ||
|
||
I'm thinking that I'll do what you said and have seperate paths | ||
for writing/reading to the socket and API's to do so that give | ||
the user the option of a boundry, basically: | ||
|
||
buffer this, but don't allow me to write until it's flushed | ||
|
||
which would allow for larger than 8k COPY rows to go into the | ||
backend. | ||
|
||
-- | ||
-Alfred Perlstein - [[email protected]|[email protected]] | ||
"I have the heart of a child; I keep it in a jar on my desk." | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -516,3 +516,131 @@ http://yi.org/peter-e/ Sweden | |
|
||
************ | ||
|
||
From [email protected] Sat Jun 3 23:31:02 2000 | ||
Received: from renoir.op.net ([email protected] [207.29.195.4]) | ||
by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id WAA28683 | ||
for <[email protected]>; Sat, 3 Jun 2000 22:31:01 -0400 (EDT) | ||
Received: from news.tht.net (news.hub.org [216.126.91.242]) by renoir.op.net (o1/$Revision: 1.14 $) with ESMTP id WAA20977 for <[email protected]>; Sat, 3 Jun 2000 22:05:07 -0400 (EDT) | ||
Received: from hub.org ([email protected] [216.126.84.1]) | ||
by news.tht.net (8.9.3/8.9.3) with ESMTP id VAD35811; | ||
Sat, 3 Jun 2000 21:54:36 -0400 (EDT) | ||
(envelope-from [email protected]) | ||
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236]) | ||
by hub.org (8.9.3/8.9.3) with ESMTP id VAA12118 | ||
for <[email protected]>; Sat, 3 Jun 2000 21:41:27 -0400 (EDT) | ||
(envelope-from [email protected]) | ||
Received: from regulus.student.UU.SE ([130.238.5.2]:61160 "EHLO | ||
regulus.its.uu.se") by merganser.its.uu.se with ESMTP | ||
id <S168006AbQFDBlC>; Sun, 4 Jun 2000 03:41:02 +0200 | ||
Received: from peter (helo=localhost) | ||
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2) | ||
id 12yPV7-0002Tp-00; Sun, 04 Jun 2000 03:46:53 +0200 | ||
Date: Sun, 4 Jun 2000 03:46:53 +0200 (CEST) | ||
From: Peter Eisentraut <[email protected]> | ||
To: [email protected] | ||
cc: [email protected] | ||
Subject: Re: [GENERAL] child table doesn't inherit PRIMARY KEY? | ||
In-Reply-To: <20000603172256.A3435@styx> | ||
Message-ID: <[email protected]> | ||
MIME-Version: 1.0 | ||
Content-Type: TEXT/PLAIN; charset=ISO-8859-1 | ||
Content-Transfer-Encoding: 8BIT | ||
X-Mailing-List: [email protected] | ||
Precedence: bulk | ||
Sender: [email protected] | ||
Status: ORr | ||
|
||
Louis-David Mitterrand writes: | ||
|
||
> When creating a child (through CREATE TABLE ... INHERIT (parent)) it | ||
> seems the child gets all of the parent's contraints _except_ its PRIMARY | ||
> KEY. Is this normal? | ||
|
||
It's kind of a bug. | ||
|
||
|
||
-- | ||
Peter Eisentraut Sernanders v�g 10:115 | ||
[email protected] 75262 Uppsala | ||
http://yi.org/peter-e/ Sweden | ||
|
||
|
||
From [email protected] Fri Jan 19 12:37:34 2001 | ||
Received: from megazone23.bigpanda.com (rfx-64-6-210-138.users.reflexcom.com [64.6.210.138]) | ||
by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id MAA28247 | ||
for <[email protected]>; Fri, 19 Jan 2001 12:37:33 -0500 (EST) | ||
Received: from localhost (sszabo@localhost) | ||
by megazone23.bigpanda.com (8.11.1/8.11.1) with ESMTP id f0JHb2H05566; | ||
Fri, 19 Jan 2001 09:37:03 -0800 (PST) | ||
Date: Fri, 19 Jan 2001 09:37:02 -0800 (PST) | ||
From: Stephan Szabo <[email protected]> | ||
To: Bruce Momjian <[email protected]> | ||
cc: [email protected] | ||
Subject: Re: [GENERAL] child table doesn't inherit PRIMARY KEY? | ||
In-Reply-To: <[email protected]> | ||
Message-ID: <[email protected]> | ||
MIME-Version: 1.0 | ||
Content-Type: TEXT/PLAIN; charset=US-ASCII | ||
Status: OR | ||
|
||
|
||
Probably, since I see it in near recent sources (and it affects | ||
UNIQUE as well. As I remember it, the last discussion on this couldn't | ||
determine what the correct behavior for unique/primary key constraints | ||
was in the inheritance case (is it a single unique hierarchy through | ||
all the tables [would be needed for fk to inheritance trees] or | ||
separate unique constraints for each table [which would be similar | ||
to how many people seem to currently use postgres inheritance as a | ||
shortcut]). | ||
|
||
On Thu, 18 Jan 2001, Bruce Momjian wrote: | ||
|
||
> Does this bug still exist? | ||
> | ||
> [ Charset ISO-8859-1 unsupported, converting... ] | ||
> > Louis-David Mitterrand writes: | ||
> > | ||
> > > When creating a child (through CREATE TABLE ... INHERIT (parent)) it | ||
> > > seems the child gets all of the parent's contraints _except_ its PRIMARY | ||
> > > KEY. Is this normal? | ||
|
||
|
||
From [email protected] Wed Jan 24 14:26:12 2001 | ||
Received: from megazone23.bigpanda.com (rfx-64-6-210-138.users.reflexcom.com [64.6.210.138]) | ||
by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id OAA26091 | ||
for <[email protected]>; Wed, 24 Jan 2001 14:26:10 -0500 (EST) | ||
Received: from localhost (sszabo@localhost) | ||
by megazone23.bigpanda.com (8.11.1/8.11.1) with ESMTP id f0OJPZ858086; | ||
Wed, 24 Jan 2001 11:25:35 -0800 (PST) | ||
Date: Wed, 24 Jan 2001 11:25:35 -0800 (PST) | ||
From: Stephan Szabo <[email protected]> | ||
To: Bruce Momjian <[email protected]> | ||
cc: PostgreSQL-development <[email protected]> | ||
Subject: Re: [GENERAL] child table doesn't inherit PRIMARY KEY? | ||
In-Reply-To: <[email protected]> | ||
Message-ID: <[email protected]> | ||
MIME-Version: 1.0 | ||
Content-Type: TEXT/PLAIN; charset=US-ASCII | ||
Status: ORr | ||
|
||
On Wed, 24 Jan 2001, Bruce Momjian wrote: | ||
|
||
> | ||
> OK, what do people want to do with this item? Add to TODO list? | ||
> | ||
> Seems making a separat unique constraint would be easy to do and be of | ||
> value to most users. | ||
|
||
The problem is that doing that will pretty much guarantee that we won't | ||
be doing foreign keys to inheritance trees without changing that behavior | ||
and we've seen people asking about adding that too. I think that this | ||
falls into the general category of "Make inheritance make sense" (Now | ||
there's a todo item :) ) Seriously, I think the work on how inheritance | ||
is going to work will decide this, maybe we end up with a real inheritance | ||
tree system and something that works like the current stuff in which case | ||
I'd say it's probably one unique for the former and one per for the | ||
latter. | ||
|
||
|
||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.