pgsql-bugs since 2002-02-23 00:00

If you find a bug, please use the bug reporting form.

Search the Archives

(enter a message-id to go directly to that message)
Advanced Search

Browse Archives

Prev | Next

Feb. 23, 2002

Thread Author Time
Re: CURRENT_TIMESTAMP not work correctly insinde a transaction. Tom Lane 00:36
Re: Bug #534: factorial function Bruce Momjian 01:06
Re: COPY when 'filename' is a directory Bruce Momjian 02:10
Re: Bug #597: ResultSet.next() throws NullPointerException Bruce Momjian 02:38
Re: COPY when 'filename' is a directory 📎 Bruce Momjian 21:45

Feb. 24, 2002

Thread Author Time
Re: COPY when 'filename' is a directory Tom Lane 01:27
Re: COPY when 'filename' is a directory Brent Verner 01:56
Re: COPY when 'filename' is a directory 📎 Brent Verner 01:59
Re: [PATCHES] COPY when 'filename' is a directory Bruce Momjian 02:03
Re: [PATCHES] COPY when 'filename' is a directory Tom Lane 02:11
Re: [PATCHES] COPY when 'filename' is a directory 📎 Bruce Momjian 02:31
Re: [PATCHES] COPY when 'filename' is a directory Tom Lane 02:41
Re: [PATCHES] COPY when 'filename' is a directory Bruce Momjian 02:47
Re: [PATCHES] COPY when 'filename' is a directory Tom Lane 03:19

Feb. 25, 2002

Thread Author Time
missing foreign key fails silently using COPY Lee Harr 00:58
Bug #602: Chinese characters query bug. pgsql-bugs 01:48
Re: Bug #602: Chinese characters query bug. Tatsuo Ishii 01:54
Re: [BUGS] Bug #602: Chinese characters query bug. Tatsuo Ishii 13:47
Re: missing foreign key fails silently using COPY Tom Lane 17:24
Re: missing foreign key fails silently using COPY Tom Lane 18:55
Re: Possible bug concerning LASTOID in 7.2 Tom Lane 23:29

Feb. 26, 2002

Thread Author Time
Re: Full bug list Justin 03:58
Re: Trying Cygwin version of PostgreSQL again Justin 04:05
COPY FROM is not 8bit clean Darcy Buskermolen 04:21
COPY FROM is not 8bit clean Darcy Buskermolen 04:37
COPY FROM is not 8bit clean Darcy Buskermolen 04:45
Re: COPY FROM is not 8bit clean Tom Lane 04:57
problems with configure connected with readline&history toxic 10:40
Re: COPY FROM is not 8bit clean Tatsuo Ishii 12:16
Bug #603: time() problems with PostgreSQL 7.2 pgsql-bugs 13:43
Bug #604: string join problem pgsql-bugs 13:50
Re: Bug #603: time() problems with PostgreSQL 7.2 Tom Lane 15:28
Re: Bug #604: string join problem Tom Lane 15:35
Re: JDBC/JSP: Strange Problem Josh Burdick 16:21
Re: COPY FROM is not 8bit clean Darcy Buskermolen 16:23
Re: COPY FROM is not 8bit clean Darcy Buskermolen 16:30
Re: Bug #604: string join problem Erol Ozcan 16:36
Re: COPY FROM is not 8bit clean Tom Lane 17:48
Re: COPY FROM is not 8bit clean Bruce Momjian 18:05
Re: COPY FROM is not 8bit clean Tom Lane 23:33

Feb. 27, 2002

Thread Author Time
Re: COPY FROM is not 8bit clean Bruce Momjian 03:09
function tree_level(varchar) (from OpenACS) no longer work under 7.2 Jean-Paul ARGUDO 08:07
SELECT statement causing terminating the backend Radek Hrabčák 11:16
cannot install postgresql 7.2 UltraMax 14:03
Re: function tree_level(varchar) (from OpenACS) no longer work under 7.2 Tom Lane 15:07
performance problems on updates on large tables with indexes Reinhard Max 16:29
Re: function tree_level(varchar) (from OpenACS) no longer work under 7.2 Jean-Paul ARGUDO 16:36
Re: performance problems on updates on large tables with indexes Tom Lane 21:41
Re: missing foreign key fails silently using COPY Tom Lane 23:04
Segmentation Fault Sidney 23:06

Feb. 28, 2002

Thread Author Time
Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin 02:53
Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane 03:57
Re: Indexes not always used after inserts/updates/vacuum analyze 📎 Michael G. Martin 04:15
Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane 04:28
Re: Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin 04:32
Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane 04:40
Re: Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin 04:41
Re: Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin 04:45
Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane 05:00
Re: Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin 05:20
postmaster problem.... Nitesh 06:25
Re: Indexes not always used after inserts/updates/vacuum Reinhard Max 11:56
Re: Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin 14:40
Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane 14:51
Re: Indexes not always used after inserts/updates/vacuum 📎 Reinhard Max 15:00
Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane 15:15
RSERV AND POSTGRESQL 7.2 free 15:55
Re: Indexes not always used after inserts/updates/vacuum Reinhard Max 16:43
Incorrect PostgreSQL 7.2 ODBC RPM for RedHat 6.2 Steve Wranovsky 18:52
Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane 21:10

March 1, 2002

Thread Author Time
Re: Indexes not always used after inserts/updates/vacuum Reinhard Max 07:06
Encoding Problem? cnliou 07:57
about catalogue tables bugs? Fouad Fezzi 09:21
Bug #605: timestamp(timestamp('a timestamp)) no longer works pgsql-bugs 09:50
cannot install postgresql 7.2 UltraMax 10:26
Re: cannot install postgresql 7.2 UltraMax 12:36
BUG: bigint and indexes ? Victor Krasinsky 13:19
Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane 14:37
Re: Bug #605: timestamp(timestamp('a timestamp)) no longer works Tom Lane 15:03
Re: Bug #605: timestamp(timestamp('a timestamp)) no longer works Thomas Lockhart 15:16
Re: Bug #605: timestamp(timestamp('a timestamp)) no longer works Thomas Lockhart 15:21
Re: Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin 16:44
Re: SELECT statement causing terminating the backend Tom Lane 21:03
Re: Bug #605: timestamp(timestamp('a timestamp)) no longer works Andrew McMillan 23:56

March 2, 2002

Thread Author Time
Gmake check problem Steven N=?ISO-8859-1?B?+vE=?=ez 04:02
Large shared_buffers freezing computers Michael G. Martin 05:02
We have visited your website shop.juni.gliwice.pl pgsql-bugs 10:54
Re: Large shared_buffers freezing computers Michael G. Martin 15:17
Make check problem with 7.2 Steven N=?ISO-8859-1?B?+vE=?=ez 23:12

March 3, 2002

Thread Author Time
Re: Make check problem with 7.2 Tom Lane 20:36

March 4, 2002

Thread Author Time
Re: Make check problem with 7.2 Steven N=?ISO-8859-1?B?+vE=?=ez 00:53
Re: Make check problem with 7.2 Steven N=?ISO-8859-1?B?+vE=?=ez 01:02
Re: Make check problem with 7.2 Tom Lane 02:15
Re: Make check problem with 7.2 Steven N=?ISO-8859-1?B?+vE=?=ez 03:35
Re: Make check problem with 7.2 Bruce Momjian 05:03
Re: Make check problem with 7.2 Steven N=?ISO-8859-1?B?+vE=?=ez 05:44
Bug #606: exec sql ifdef, ... incorrect parsing pgsql-bugs 06:57
Re: Indexes not always used after inserts/updates/vacuum Reinhard Max 11:10
Re: Sun Solaris 2.5.1 Seg Faults PostgreSQL7.1.3 build com Riendeau, Mike 19:12
Bug #607: to_date() function bug pgsql-bugs 19:21
Re: BUG: bigint and indexes ? Stephan Szabo 21:00
Re: Bug #607: to_date() function bug Tom Lane 21:54

March 5, 2002

Thread Author Time
Re: Encoding Problem? Tatsuo Ishii 01:01
Re: postmaster problem.... Justin 02:50
JDBC Trouble when exception appears . Nicolas Paymal 09:52

March 6, 2002

Thread Author Time
regression - postgresql 7.2 on power pc/linux Arkadiusz Miskiewicz 09:18
Bug #608: cache lookup failed pgsql-bugs 14:33
Re: Bug #608: cache lookup failed Tom Lane 18:35

March 7, 2002

Thread Author Time
referential constraint bug Eric Lu 00:49
Re: Bug #608: cache lookup failed Laurent FAILLIE 10:47
Re: Bug #608: cache lookup failed Tom Lane 15:05
Re: regression - postgresql 7.2 on power pc/linux Stephan Szabo 15:44
Re: Bug #608: cache lookup failed Laurent FAILLIE 16:00
Re: Bug #608: cache lookup failed Tom Lane 16:07
Re: Bug #608: cache lookup failed Laurent FAILLIE 16:36
Bug #609: CREATE TABLE with implicit index should not fail if index already exists pgsql-bugs 17:27
Bug #610: collation fails sorting because of strcoll() bug pgsql-bugs 19:36
Re: Bug #610: collation fails sorting because of strcoll() bug Tom Lane 21:21

March 8, 2002

Thread Author Time
Re: libpq not reentrant Bruce Momjian 01:09
Re: Bug #608: cache lookup failed Juliano Ignacio 17:44

March 9, 2002

Thread Author Time
Fwd: Bug in getTimestamp() of PostgreSQL JDBC driver? Peter T Mount 11:50

March 11, 2002

Thread Author Time
comparing null value in plpgsql. Bhuvan A 05:14
Re: comparing null value in plpgsql. Stephan Szabo 06:10
Re: comparing null value in plpgsql. bhuvanbk 07:03
Bug #611: configure script produces incorrect results under IRIX pgsql-bugs 07:08
Re: comparing null value in plpgsql. Bhuvan A 07:21
Bug #612: PostgreSQL 7.2 does not build according to documentation under IRIX w/ MIPSpro pgsql-bugs 08:09
Re: comparing null value in plpgsql. Stephan Szabo 08:15
[No subject] Bhuvan A 10:26
Re: Bug #608: cache lookup failed Yury Bokhoncovich 14:23
Re: Bug #611: configure script produces incorrect results under IRIX Tom Lane 14:28
Re: Yury Bokhoncovich 14:33
Re: Peter Eisentraut 16:46
Re: Stephan Szabo 17:02
Critical: Pgsql inserts bad timestamp (seconds 60.00) - causes failing of backup-restore Mozilla at Marela 17:59
Re: Juliano Ignacio 20:12
Bug #613: Sequence values fall back to previously checkpointed value after crash pgsql-bugs 21:59
Re: Bug #613: Sequence values fall back to previously checkpointed Bruce Momjian 23:02

March 12, 2002

Thread Author Time
Re: Bug #613: Sequence values fall back to previously checkpointed Tom Lane 05:17
Re: Bug #613: Sequence values fall back to previously checkpointed Justin 06:28
Re: Bug #613: Sequence values fall back to previously checkpointed bgrimm 13:38
Case sensitive table names ? Per Winkvist 19:32
Build of PostgreSQL under Irix Robert E. Bruccoleri 19:41
Re: Bug #613: Sequence values fall back to previously checkpointed Bruce Momjian 22:49
Re: Bug #613: Sequence values fall back to previously checkpointed Tom Lane 23:36
Re: Bug #613: Sequence values fall back to previously checkpointed Bruce Momjian 23:46
Re: Bug #613: Sequence values fall back to previously checkpointed Bruce Momjian 23:51

March 13, 2002

Thread Author Time
Re: Bug #613: Sequence values fall back to previously checkpointed Tom Lane 15:31
Re: referential constraint bug Stephan Szabo 16:13
Re: Bug #613: Sequence values fall back to previously checkpointed Ben Grimm 16:28
SERIAL silently trunctates sequence name to 31 characters Ward Vandewege 16:47
Re: Bug #613: Sequence values fall back to previously checkpointed Tom Lane 19:39
Case sensitive table names ? Per Winkvist 20:10
Re: referential constraint bug Bruce Momjian 20:31
Re: Bug #613: Sequence values fall back to previously chec Mikheev, Vadim 21:03
Re: referential constraint bug Stephan Szabo 21:54
Re: Bug #613: Sequence values fall back to previously chec kpointed Tom Lane 22:00
Re: Bug #613: Sequence values fall back to previously chec kpointed Tom Lane 22:29
Re: Bug #613: Sequence values fall back to previously checkpointed Ben Grimm 22:32
Re: Bug #613: Sequence values fall back to previously chec Mikheev, Vadim 22:34
Re: Case sensitive table names ? Peter Eisentraut 23:06

March 14, 2002

Thread Author Time
sequence havn't been dropped. Bhuvan A 05:11
Re: sequence havn't been dropped. Peter Eisentraut 05:53
Unable to identify an operator '=' for types 'numeric' and 'float8' Sridhar Bhamidi 08:12
Bug #614: Incorrect parse with time function pgsql-bugs 11:15
problem with new postgresql driver awais 11:32
Re: comparing null value in plpgsql. Tom Pfau 15:12
Re: Bug #613: Sequence values fall back to previously chec Tom Pfau 15:26
Re: Bug #613: Sequence values fall back to previously chec bgrimm 15:29
Re: problem with new postgresql driver Stephan Szabo 15:33
Bug #615: Bug in ilke and ~~* Sql expression pgsql-bugs 16:22
Re: Bug #613: Sequence values fall back to previously chec Tom Lane 17:27
Re: [HACKERS] Bug #613: Sequence values fall back to previously chec Dave Cramer 17:54
Re: Bug #615: Bug in ilke and ~~* Sql expression Tom Lane 19:20
Re: [HACKERS] Bug #613: Sequence values fall back to previously chec Tom Lane 19:33
Storage problems Daniel Malaquias de Freitas 20:54
Re: referential constraint bug Bruce Momjian 22:37
Re: Bug #613: Sequence values fall back to previously chec Ben Grimm 22:47
Re: Bug #613: Sequence values fall back to previously chec Tom Lane 23:58

March 15, 2002

Thread Author Time
Re: Bug #613: Sequence values fall back to previously chec Mikheev, Vadim 00:17
Re: Bug #613: Sequence values fall back to previously chec 'Ben Grimm' 01:55
Re: Bug #613: Sequence values fall back to previously chec Vadim Mikheev 09:05
Bug #616: Alter table add foreign key pgsql-bugs 12:24
Bug #617: In SQL the tableowner is not allowed pgsql-bugs 12:26
ALTER TABLE Problem dirk.jacobs 12:26
Bug #618: Incorrect error codes pgsql-bugs 12:27
Bug #619: Not possible to specify foreign key name pgsql-bugs 12:36
Re: Bug #616: Alter table add foreign key Stefano Reksten 12:39
Re: Bug #613: Sequence values fall back to previously chec 'Ben Grimm' 13:23
Bug #620: create index ... (date_part('year', d)) fails pgsql-bugs 13:52
[No subject] 📎 Viacheslav N Tararin 14:09
Re: Bug #613: Sequence values fall back to previously chec Tom Lane 14:34
Re: Bug #613: Sequence values fall back to previously chec 📎 Tom Lane 14:39
Re: [HACKERS] Bug #613: Sequence values fall back to previously Bruce Momjian 15:43
Re: [HACKERS] Bug #613: Sequence values fall back to previously Bruce Momjian 15:44
Re: Bug #613: Sequence values fall back to previously chec 'Ben Grimm' 15:44
Re: Bug #614: Incorrect parse with time function Thomas Lockhart 15:47
Re: Bug #613: Sequence values fall back to previously chec Tom Lane 16:03
Re: Bug #617: In SQL the tableowner is not allowed Peter Eisentraut 16:21
Re: Bug #619: Not possible to specify foreign key name Stephan Szabo 16:25

Browse Archives

Prev | Next