Peripheral Links

• Home
• About
• Download
• Documentation
• Community
• Developers
• Support
• Your account

pgsql-hackers since 2000-07-15 00:00

July 15, 2000

• Re: PgAccess diagrams (was: Re: Just committed some changes...) Thomas Lockhart (01:46)
• Re: Latest parser changes Thomas Lockhart (02:04)
• Re: Re: Latest parser changes Tom Lane (02:09)
• RE: PgAccess diagrams (was: Re: Just committed some changes...) Magnus Hagander (15:03)
• Re: PgAccess diagrams (was: Re: Just committed some changes...) Constantin Teodorescu (15:51)
• Re: Problems compiling CVS on Solaris. Peter Eisentraut (21:33)

July 16, 2000

• pg_dump with BLOBS & V7.0.2 fix Philip Warner (03:34)
• pg_dump with BLOBS & V7.0.2 UPDATED Philip Warner (10:49)
• Automatic dependency tracking is here Peter Eisentraut (14:51)
• Keyword indexing code for contrib Andrew McMillan (21:24)
• Re: Keyword indexing code for contrib Bruce Momjian (23:24)

July 17, 2000

• macaddr type (fwd) Larry Rosenman (02:33)
• Re: macaddr type (fwd) Tom Lane (04:23)
• Re: AW: fmgr changes not yet ported to AIX Tom Lane (04:55)
• Should PG backend know how to represent metadata? Philip Warner (06:21)
• Re: Should PG backend know how to represent metadata? Chris Bitmead (06:30)
• Re: Should PG backend know how to represent metadata? Tom Lane (06:43)
• Re: Should PG backend know how to represent metadata? Philip Warner (06:52)
• Re: Should PG backend know how to represent metadata? Philip Warner (07:06)
• Re: Should PG backend know how to represent metadata? Philip Warner (07:43)
• Re: pltcl regress test? Tom Lane (14:36)
• Re: Should PG backend know how to represent metadata? eisentrp (14:45)
• Re: Should PG backend know how to represent metadata? Tom Lane (14:46)
• Update: mac.c update, patch now on ftp Larry Rosenman (16:10)
• Re: Should PG backend know how to represent metadata? Philip Warner (16:30)
• Re: Should PG backend know how to represent metadata? Philip Warner (16:47)
• psql eating backslashes Jan Wieck (17:01)
• Re: lost records ! Tom Lane (17:12)
• Re: Update: mac.c update, patch now on ftp Bruce Momjian (18:13)
• Re: psql eating backslashes Peter Eisentraut (18:30)
• RE: Update: mac.c update, patch now on ftp Larry Rosenman (18:37)
• Re: Update: mac.c update, patch now on ftp Bruce Momjian (18:42)
• TUPLE SIZE HELP Thomas Swan (18:58)
• Re: TUPLE SIZE HELP B. Palmer (20:06)
• Re: TUPLE SIZE HELP Thomas Swan (20:55)
• Re: TUPLE SIZE HELP Tom Lane (21:35)
• Re: psql eating backslashes Tom Lane (21:42)
• Re: Update: mac.c update, patch now on ftp Tom Lane (21:46)
• Re: TUPLE SIZE HELP Thomas Swan (21:56)
• Re: Should PG backend know how to represent metadata? Peter Eisentraut (22:29)
• Re: Should PG backend know how to representmetadata? Chris Bitmead (23:09)
• TOAST vs arrays Tom Lane (23:14)
• libpgtcl on aix Tim Dunnington (23:20)

July 18, 2000

• Re: Should PG backend know how to representmetadata? Philip Warner (01:14)
• Re: Should PG backend know how to represent metadata? Philip Warner (01:36)
• Re: Update: mac.c update, patch now on ftp Larry Rosenman (01:55)
• Re: Update: mac.c update, patch now on ftp Thomas Lockhart (02:54)
• Warnings triggered by recent includefile cleanups Tom Lane (04:21)
• Re: TUPLE SIZE HELP Jan Wieck (09:10)
• Re: TOAST vs arrays Jan Wieck (10:58)
• Re: pltcl regress test? Jan Wieck (11:27)
• Untrusted PL/Tcl? Jan Wieck (11:36)
• Re: Update: mac.c update, patch now on ftp Larry Rosenman (11:50)
• Re: Untrusted PL/Tcl? Lamar Owen (11:54)
• Re: Untrusted PL/Tcl? ts (12:12)
• FlushRelationBuffers returned -2 Magnus Hagander (13:59)
• Re: TOAST vs arrays Tom Lane (14:43)
• Re: Untrusted PL/Tcl? Tom Lane (14:52)
• Re: FlushRelationBuffers returned -2 Tom Lane (15:08)
• RE: FlushRelationBuffers returned -2 Magnus Hagander (16:21)
• Re: Untrusted PL/Tcl? Jan Wieck (16:33)
• Shared library search paths Peter Eisentraut (18:18)
• Re: Warnings triggered by recent includefile cleanups Peter Eisentraut (18:28)
• MySQL comparison Ferruccio Zamuner (20:10)
• PRIMARY KEY & INHERITANCE (fwd) Ferruccio Zamuner (20:11)
• btree split logic is fragile in the presence of large index items Tom Lane (20:48)
• Re: Untrusted PL/Tcl? Tom Lane (20:55)
• Re: Warnings triggered by recent includefile cleanups Tom Lane (21:10)
• Re: Shared library search paths Mark Dalphin (21:55)
• RE: btree split logic is fragile in the presence of large index items Mikheev, Vadim (22:47)
• Re: Shared library search paths Oliver Elphick (22:47)
• linux.h Lamar Owen (23:00)
• In the news... Lamar Owen (23:03)
• Re: TUPLE SIZE HELP Hannu Krosing (23:36)
• Re: btree split logic is fragile in the presence of large index items Tom Lane (23:47)
• Re: TUPLE SIZE HELP The Hermit Hacker (23:50)

July 19, 2000

• Re: TUPLE SIZE HELP Vince Vielhaber (00:00)
• RE: btree split logic is fragile in the presence of large index items Mikheev, Vadim (00:18)
• Re: TUPLE SIZE HELP The Hermit Hacker (00:41)
• Re: [PORTS] Shared library search paths The Hermit Hacker (01:48)
• Re: [PORTS] Shared library search paths Thomas Lockhart (01:52)
• Re: MySQL comparison Chris Bitmead (03:52)
• RE: btree split logic is fragile in the presence of large index items Hiroshi Inoue (03:54)
• Re: PRIMARY KEY & INHERITANCE (fwd) Chris Bitmead (03:56)
• Re: MySQL comparison Tom Lane (04:51)
• Re: [HACKERS] Re: PRIMARY KEY & INHERITANCE (fwd) Stephan Szabo (05:25)
• Docs organized as a "set" Thomas Lockhart (06:42)
• System tables since 7.0.0 Peter Mount (06:53)
• RE: System tables since 7.0.0 Peter Mount (07:07)
• The query cache - first snapshot (long) Karel Zak (08:16)
• Re: pg_dump with BLOBS & V7.0.2 UPDATED Pavel Janík ml. (09:11)
• Re: MySQL comparison Peter Vazsonyi (10:19)
• Re: [HACKERS] Re: pg_dump with BLOBS & V7.0.2 UPDATED Pavel Janík ml. (11:18)
• Re: Untrusted PL/Tcl? Jan Wieck (12:49)
• Re: [HACKERS] Re: PRIMARY KEY & INHERITANCE (fwd) Stephan Szabo (14:26)
• Re: System tables since 7.0.0 Tom Lane (15:12)
• Hello PL/Python Karel Zak (15:24)
• RE: System tables since 7.0.0 Peter Mount (15:26)
• Re: btree split logic is fragile in the presence of lar ge index items Tom Lane (15:45)
• Re: btree split logic is fragile in the presence of large index items Peter Eisentraut (16:27)
• Re: Warnings triggered by recent includefile cleanups Peter Eisentraut (16:28)
• Re: btree split logic is fragile in the presence of large index items Tom Lane (16:52)
• RE: btree split logic is fragile in the presence of lar ge index items Mikheev, Vadim (16:59)
• Re: btree split logic is fragile in the presence of lar ge index items Tom Lane (18:13)
• Re: Untrusted PL/Tcl? Mikhail Terekhov (19:06)
• Re: Shared library search paths Peter Eisentraut (22:46)
• About these IPC parameters Peter Eisentraut (22:46)
• Re: [HACKERS] Re: PRIMARY KEY & INHERITANCE (fwd) Chris Bitmead (23:43)
• RE: btree split logic is fragile in the presence of lar ge index items Hiroshi Inoue (23:45)

July 20, 2000

• RE: btree split logic is fragile in the presence of lar ge index items Mikheev, Vadim (00:17)
• Re: Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd) Stephan Szabo (00:18)
• Re: btree split logic is fragile in the presence of lar ge index items Tom Lane (00:21)
• Re: Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd) Chris Bitmead (00:31)
• RE: btree split logic is fragile in the presence of lar ge index items Hiroshi Inoue (00:41)
• Re: Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd) Stephan Szabo (00:50)
• RE: btree split logic is fragile in the presence of lar ge index items Mikheev, Vadim (01:39)
• mac.c Larry Rosenman (02:14)
• Re: [HACKERS] Re: PRIMARY KEY & INHERITANCE (fwd) Tom Lane (04:22)
• Re: About these IPC parameters Tom Lane (04:50)
• Re: [HACKERS] Re: PRIMARY KEY & INHERITANCE (fwd) Chris Bitmead (04:56)
• Re: btree split logic is fragile in the presence of lar ge index items Tom Lane (05:08)
• Re: Update: mac.c update, patch now on ftp Thomas Lockhart (06:07)
• Re: Update: mac.c update, patch now on ftp Larry Rosenman (06:33)
• 8Ko limitation Xavier ZIMMERMANN (07:42)
• Re: Shared library search paths Oliver Elphick (07:53)
• Re: [HACKERS] 8Ko limitation Karel Zak (08:00)
• Re: Re: [HACKERS] 8Ko limitation Stephane Bortzmeyer (08:35)
• Re: Re: [HACKERS] 8Ko limitation Jules Bean (08:52)
• Re: Re: [HACKERS] 8Ko limitation Karel Zak (09:02)
• Re: Hello PL/Python Hannu Krosing (09:30)
• Re: Hello PL/Python Karel Zak (10:40)
• Re: varbit type Adriaan Joubert (11:11)
• Loading binary data into the database Adriaan Joubert (11:36)
• locale changes Karel Zak (12:18)
• pg_dump with BLOBs UPDATED Philip Warner (13:24)
• PGLZ memory problems fixed Jan Wieck (14:23)
• Re: Re: [HACKERS] 8Ko limitation Tom Lane (14:52)
• Re: Hello PL/Python Tom Lane (14:58)
• Re: Loading binary data into the database Tom Lane (15:08)
• Re: locale changes Tom Lane (15:16)
• Re: [HACKERS] 8Ko limitation Tom Lane (15:17)
• About TOAST and indices Jan Wieck (15:20)
• Re: Loading binary data into the database Adriaan Joubert (15:24)
• Re: locale changes Karel Zak (15:31)
• Re: Hello PL/Python Jan Wieck (15:39)
• Stupid Me... Larry Rosenman (15:40)
• Re: Loading binary data into the database Tom Lane (15:43)
• Re: locale changes Tom Lane (15:48)
• Re: About these IPC parameters The Hermit Hacker (15:50)
• Re: About TOAST and indices Tom Lane (15:51)
• Re: 8Ko limitation Justin Hickey (16:06)
• How PostgreSQL's floating-point hurts everyone everywhere Peter Eisentraut (16:10)
• Re: locale changes Karel Zak (16:16)
• Re: About TOAST and indices Jan Wieck (16:41)
• Re: How PostgreSQL's floating-point hurts everyone everywhere Thomas Lockhart (16:47)
• Re: How PostgreSQL's floating-point hurts everyone everywhere Henry B. Hotz (17:03)
• Re: How PostgreSQL's floating-point hurts everyone everywhere Jan Wieck (17:28)
• Re: Re: [HACKERS] 8Ko limitation Brook Milligan (18:01)
• Re: Re: [HACKERS] 8Ko limitation Erich (21:05)
• RE: btree split logic is fragile in the presence of lar ge index items Mikheev, Vadim (21:30)
• my stupidity Larry Rosenman (23:40)

July 21, 2000

• Re: [PATCHES] locale changes Peter Eisentraut (00:46)
• Re: my stupidity John McKown (05:01)
• Re: my stupidity Larry Rosenman (05:10)
• Re: Loading binary data into the database Adriaan Joubert (05:17)
• Re: How PostgreSQL's floating-point hurts everyone everywhere Tom Lane (06:57)
• Re: How PostgreSQL's floating-point hurts everyone everywhere Thomas Lockhart (07:08)
• Re: Re: [HACKERS] 8Ko limitation Stephane Bortzmeyer (07:39)
• TOAST & vacuum Jan Wieck (10:30)
• Geometry test broken Jan Wieck (11:11)
• Re: Hello PL/Python Hannu Krosing (11:40)
• Re: [HACKERS] 8Ko limitation Hannu Krosing (11:56)
• Re: Hello PL/Python Tom Lane (14:10)
• pg_dump, libdump, dump API, & backend again Philip Warner (15:08)
• Re: Shared library search paths Oliver Elphick (15:51)
• Re: TOAST & vacuum Tom Lane (18:29)
• Re: About these IPC parameters Peter Eisentraut (18:29)
• Re: About these IPC parameters Peter Eisentraut (18:30)
• Re: About these IPC parameters The Hermit Hacker (18:34)
• Re: About these IPC parameters Henry B. Hotz (18:47)
• Vaccuum allows read access? Alfred Perlstein (18:52)
• Re: Vaccuum allows read access? The Hermit Hacker (18:56)
• Re: Vaccuum allows read access? Bruce Momjian (18:58)
• Re: About these IPC parameters Tom Lane (18:59)
• Re: Vaccuum allows read access? Tom Lane (19:15)

July 22, 2000

• Re: Geometry test broken Thomas Lockhart (01:43)
• Re: pg_dump, libdump, dump API, & backend again Peter Eisentraut (01:47)
• Re: TOAST & vacuum Jan Wieck (09:28)
• Re: Vaccuum allows read access? Jan Wieck (11:20)
• Re: Hello PL/Python The Hermit Hacker (12:50)
• Re: Vaccuum allows read access? Tom Lane (16:09)

July 23, 2000

• Re: lost records --- problem identified! Tom Lane (00:09)
• Re: pg_dump, libdump, dump API, & backend again Philip Warner (12:54)
• TODO updates Peter Eisentraut (12:58)
• Re: TODO updates Philip Warner (13:11)
• INET/CIDR types Larry Rosenman (14:00)
• mac.c Larry Rosenman (14:03)
• Re: TODO updates Tom Lane (16:36)
• Re: TODO updates Tom Lane (17:18)
• Re: mac.c Thomas Lockhart (20:23)