Home > mailing lists

Mailing lists [pgsql-hackers]

17 November 2000

00:01 Re: [rfc] new CREATE FUNCTION (and more) Philip Warner
00:04 Re: [rfc] new CREATE FUNCTION (and more) Marko Kreen
00:09 Re: coding style guidelines? Bruce Momjian
00:21 Re: [rfc] new CREATE FUNCTION (and more) Tom Lane
00:27 Re: [PATCHES] A Patch for MIC to EUC_TW code converting inmbsupport Tatsuo Ishii
00:33 Re: Re: [PATCHES] A Patch for MIC to EUC_TW code converting in mbsupport Tatsuo Ishii
00:37 Re: [rfc] new CREATE FUNCTION (and more) Philip Warner
01:12 Re: [rfc] new CREATE FUNCTION (and more) Tom Lane
01:56 Re: [rfc] new CREATE FUNCTION (and more) Philip Warner
02:08 Re: [rfc] new CREATE FUNCTION (and more) Tom Lane
03:28 Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) Tom Samplonius
04:36 Failure to recognise new database Grant Finnemore
05:20 Re: Failure to recognise new database Thomas Lockhart
05:40 Re: Failure to recognise new database Tom Lane
07:06 Re: Failure to recognise new database Grant Finnemore
07:31 AW: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) Zeugswetter Andreas SB
07:36 AW: AW: AW: AW: Coping with 'C' vs 'newC' function lang uage nam esh Zeugswetter Andreas SB
08:45 Re: AW: Coping with 'C' vs 'newC' function language namesh Philip Warner
10:17 Fundamental change of locking behavior in 7.1 Zeugswetter Andreas SB
11:31 Re: Failure to recognise new database Thomas Lockhart
12:27 Re: Unhappy thoughts about pg_dump and objects inherited from template1 Jan Wieck
12:27 Re: Coping with 'C' vs 'newC' function language names Jan Wieck
13:53 Re: Varchar standard compliance Peter Eisentraut
14:08 AW: Coping with 'C' vs 'newC' function language names Zeugswetter Andreas SB
14:10 Re: Coping with 'C' vs 'newC' function language names Peter Eisentraut
14:18 Re: Database startup info Tom Lane
14:29 Re: Varchar standard compliance Tom Lane
14:54 Re: Coping with 'C' vs 'newC' function language names Tom Lane
15:22 AW: Coping with 'C' vs 'newC' function language names Zeugswetter Andreas SB
15:24 Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) Bruce Momjian
15:42 Re: Coping with 'C' vs 'newC' function language names Bruce Momjian
15:46 Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) Larry Rosenman
16:06 Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) Bruce Momjian
16:06 Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) Larry Rosenman
16:15 Re: Coping with 'C' vs 'newC' function language names Peter Eisentraut
16:21 Re: Coping with 'C' vs 'newC' function language names Peter Eisentraut
16:50 Re: Varchar standard compliance Peter Eisentraut
16:59 Re: AW: Coping with 'C' vs 'newC' function language namesh Ross J. Reedstrom
18:01 Re: Coping with 'C' vs 'newC' function language names Tom Lane
20:32 Re: [rfc] new CREATE FUNCTION (and more) Tom Lane
20:36 RE: Fundamental change of locking behavior in 7.1 Hiroshi Inoue
20:40 Re: Coping with 'C' vs 'newC' function language names Thomas Lockhart
20:48 Re: Coping with 'C' vs 'newC' function language names Hannu Krosing
20:53 Re: Coping with 'C' vs 'newC' function language names Bruce Momjian
20:53 Re: Coping with 'C' vs 'newC' function language names Bruce Momjian
21:21 Courses Abe
22:42 location of Unix socket Oliver Elphick
22:51 Re: location of Unix socket Alfred Perlstein
23:02 Re: location of Unix socket Nathan Myers
23:10 Re: Varchar standard compliance Tom Lane
23:14 Re: Fundamental change of locking behavior in 7.1 Tom Lane
23:34 Re: location of Unix socket Bruce Momjian