• Text Size: Normal / Large
• Donate
• Contact

Section Navigation

• Community
• Contributors
• Mailing Lists
  • Subscribe
  • User lists
    • pgsql-admin
    • pgsql-advocacy
    • pgsql-announce
    • pgsql-bugs
    • pgsql-docs
    • pgsql-general
    • pgsql-jobs
    • pgsql-novice
    • pgsql-performance
    • pgsql-php
    • pgsql-sql
    • pgsql-students
  • Developer lists
  • Regional lists
  • Associations
  • User groups
  • Project lists
  • Inactive lists
• IRC
• Featured Users
• International Sites
• Propaganda
• Resources
• Weekly News
• Community login
  • Profile
  • Lost password

pgsql-bugs 2002-03 Chronological Index (1/1)

• Thread Index
• [Prev Page]
• [Next Page]

• 29 March 2002
  • Re: Bug #627: Tom Lane (14:52)
  • Re: Bug #627: Stephan Szabo (13:59)
  • Bug #627: pgsql-bugs (07:27)
• 28 March 2002
  • Bug #626: Query with View not returning proper results pgsql-bugs (00:17)
• 27 March 2002
  • Re: Bug #625: bytea data type problem/bug Joe Conway (21:27)
  • Bug #625: bytea data type problem/bug pgsql-bugs (20:25)
  • Re: Inconsistant use of index. Ron Mayer (06:47)
• 26 March 2002
  • Re: Inconsistant use of index. Tom Lane (19:59)
  • Re: Inconsistant use of index. Michael G. Martin (18:10)
  • Re: Inconsistant use of index. Ron Mayer (18:08)
  • Re: postmaster crash Michael Beckstette (18:03)
  • Re: postmaster crash Tom Lane (17:46)
  • Re: Inconsistant use of index. Tom Lane (17:37)
  • postmaster crash Michael Beckstette (17:17)
  • Inconsistant use of index. Ron Mayer (17:03)
  • Installing postgres Vaishakhi Ajmera (16:09)
  • Re: Bug #624: case sensitivity in pg_dumpall Tom Lane (15:34)
  • Bug #624: case sensitivity in pg_dumpall pgsql-bugs (13:53)
• 25 March 2002
  • Re: Bug #623: Compling 7.2 on a Tru64 V5.1 UNIX Peter Eisentraut (22:41)
  • Bug #623: Compling 7.2 on a Tru64 V5.1 UNIX pgsql-bugs (22:27)
• 22 March 2002
  • Re: 7.2 crash... Bruce Momjian (05:05)
  • Re: 7.2 crash... Tom Lane (04:23)
• 20 March 2002
  • Re: 7.2 crash... Tom Lane (05:25)
  • Re: Bug #612: PostgreSQL 7.2 does not build according to documentation under IRIX w/ MIPSpro Robert E. Bruccoleri (00:50)
• 19 March 2002
  • Re: Storage problems Tom Lane (23:56)
  • Problem with psql frontend Sullivan,Deric [CMC] (15:25)
  • Re: referential constraint bug Bruce Momjian (02:57)
  • Re: psql's \r does not reset parenthesis depth counter Bruce Momjian (00:13)
• 18 March 2002
  • Bug #622: jdbc driver exception: failed to get datetime field from a table pgsql-bugs (17:18)
  • Re: Bug #621: why postgreSQL stored databases in Darcy Buskermolen (16:54)
  • Re: Bug #612: PostgreSQL 7.2 does not build according to Peter Eisentraut (16:34)
  • Re: Bug #612: PostgreSQL 7.2 does not build according to documentation under IRIX w/ MIPSpro Tom Lane (15:16)
  • Re: Bug #612: PostgreSQL 7.2 does not build according to Jonathan C. Patschke (06:58)
  • Re: Bug #612: PostgreSQL 7.2 does not build according to documentation under IRIX w/ MIPSpro Tom Lane (06:06)
• 17 March 2002
  • Re: psql's \r does not reset parenthesis depth counter Peter Eisentraut (21:51)
  • psql's \r does not reset parenthesis depth counter Tom Lane (18:12)
  • 7.2 crash... Rod Taylor (00:56)
• 16 March 2002
  • Bug #621: why postgreSQL stored databases in digital filenames? pgsql-bugs (17:18)
  • [no subject] minfrin(at)sharp(dot)fm (15:32)
• 15 March 2002
  • Re: Bug #613: Sequence values fall back to previously chec Mikheev, Vadim (18:36)
  • Re: Bug #620: create index ... (date_part('year', d)) fails Stephan Szabo (16:27)
  • Re: Bug #619: Not possible to specify foreign key name Stephan Szabo (16:25)
  • Re: Bug #617: In SQL the tableowner is not allowed Peter Eisentraut (16:17)
  • Re: Bug #613: Sequence values fall back to previously chec Tom Lane (16:06)
  • Re: Bug #614: Incorrect parse with time function Thomas Lockhart (15:47)
  • Re: Bug #613: Sequence values fall back to previously chec 'Ben Grimm' (15:44)
  • Re: [HACKERS] Bug #613: Sequence values fall back to previously Bruce Momjian (15:44)
  • Re: [HACKERS] Bug #613: Sequence values fall back to previously Bruce Momjian (15:43)
  • Re: Bug #613: Sequence values fall back to previously chec Tom Lane (14:41)
  • Re: Bug #613: Sequence values fall back to previously chec Tom Lane (14:37)
  • [no subject] Viacheslav N Tararin (14:10)
  • Bug #620: create index ... (date_part('year', d)) fails pgsql-bugs (13:52)
  • Re: Bug #613: Sequence values fall back to previously chec 'Ben Grimm' (13:23)
  • Re: Bug #616: Alter table add foreign key Stefano Reksten (12:37)
  • Bug #619: Not possible to specify foreign key name pgsql-bugs (12:36)
  • Bug #618: Incorrect error codes pgsql-bugs (12:27)
  • Bug #617: In SQL the tableowner is not allowed pgsql-bugs (12:26)
  • Bug #616: Alter table add foreign key pgsql-bugs (12:24)
  • ALTER TABLE Problem dirk . jacobs (12:20)
  • Re: Bug #613: Sequence values fall back to previously chec Vadim Mikheev (09:04)
  • Re: Bug #613: Sequence values fall back to previously chec 'Ben Grimm' (01:55)
  • Re: Bug #613: Sequence values fall back to previously chec Mikheev, Vadim (00:17)
  • Re: Bug #613: Sequence values fall back to previously chec Tom Lane (00:00)
• 14 March 2002
  • Re: Bug #613: Sequence values fall back to previously chec Ben Grimm (22:47)
  • Re: referential constraint bug Bruce Momjian (22:38)
  • Storage problems Daniel Malaquias de Freitas (20:53)
  • Re: [HACKERS] Bug #613: Sequence values fall back to previously chec Tom Lane (19:36)
  • Re: Bug #615: Bug in ilke and ~~* Sql expression Tom Lane (19:20)
  • Re: [HACKERS] Bug #613: Sequence values fall back to previously chec Dave Cramer (17:55)
  • Re: Bug #613: Sequence values fall back to previously chec Tom Lane (17:30)
  • Bug #615: Bug in ilke and ~~* Sql expression pgsql-bugs (16:22)
  • Re: problem with new postgresql driver Stephan Szabo (15:33)
  • Re: Bug #613: Sequence values fall back to previously chec bgrimm (15:29)
  • Re: Bug #613: Sequence values fall back to previously chec Tom Pfau (15:17)
  • Re: comparing null value in plpgsql. Tom Pfau (15:03)
  • problem with new postgresql driver awais (11:30)
  • Bug #614: Incorrect parse with time function pgsql-bugs (11:15)
  • Unable to identify an operator '=' for types 'numeric' and 'float8' Sridhar Bhamidi (08:17)
  • Re: sequence havn't been dropped. Peter Eisentraut (05:49)
  • sequence havn't been dropped. Bhuvan A (05:15)
• 13 March 2002
  • Re: Case sensitive table names ? Peter Eisentraut (23:02)
  • Re: Bug #613: Sequence values fall back to previously chec Mikheev, Vadim (22:34)
  • Re: Bug #613: Sequence values fall back to previously checkpointed Ben Grimm (22:32)
  • Re: Bug #613: Sequence values fall back to previously chec kpointed Tom Lane (22:31)
  • Re: Bug #613: Sequence values fall back to previously chec kpointed Tom Lane (22:03)
  • Re: referential constraint bug Stephan Szabo (21:54)
  • Re: Bug #613: Sequence values fall back to previously chec Mikheev, Vadim (21:03)
  • Re: referential constraint bug Bruce Momjian (20:31)
  • Case sensitive table names ? Per Winkvist (20:12)
  • Re: Bug #613: Sequence values fall back to previously checkpointed Tom Lane (19:41)
  • SERIAL silently trunctates sequence name to 31 characters Ward Vandewege (16:47)
  • Re: Bug #613: Sequence values fall back to previously checkpointed Ben Grimm (16:28)
  • Re: referential constraint bug Stephan Szabo (16:13)
  • Re: Bug #613: Sequence values fall back to previously checkpointed Tom Lane (15:33)
• 12 March 2002
  • Re: Bug #613: Sequence values fall back to previously checkpointed Bruce Momjian (23:53)
  • Re: Bug #613: Sequence values fall back to previously checkpointed Bruce Momjian (23:47)
  • Re: Bug #613: Sequence values fall back to previously checkpointed Tom Lane (23:38)
  • Re: Bug #613: Sequence values fall back to previously checkpointed Bruce Momjian (22:49)
  • Build of PostgreSQL under Irix Robert E. Bruccoleri (19:36)
  • Case sensitive table names ? Per Winkvist (19:34)
  • Re: Bug #613: Sequence values fall back to previously checkpointed bgrimm (13:38)
  • Re: Bug #613: Sequence values fall back to previously checkpointed Justin (06:35)
  • Re: Bug #613: Sequence values fall back to previously checkpointed Tom Lane (05:19)
• 11 March 2002
  • Re: Bug #613: Sequence values fall back to previously checkpointed Bruce Momjian (23:02)
  • Bug #613: Sequence values fall back to previously checkpointed value after crash pgsql-bugs (21:59)
  • Re: Juliano Ignacio (20:12)
  • Critical: Pgsql inserts bad timestamp (seconds 60.00) - causes failing of backup-restore Mozilla at Marela (18:00)
  • Re: Stephan Szabo (17:02)
  • Re: Peter Eisentraut (16:42)
  • Re: Yury Bokhoncovich (14:46)
  • Re: Bug #608: cache lookup failed Yury Bokhoncovich (14:36)
  • Re: Bug #611: configure script produces incorrect results under IRIX Tom Lane (14:28)
  • [no subject] Bhuvan A (10:31)
  • Re: comparing null value in plpgsql. Stephan Szabo (08:15)
  • 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. Bhuvan A (07:26)
  • Re: comparing null value in plpgsql. bhuvanbk (07:09)
  • Bug #611: configure script produces incorrect results under IRIX pgsql-bugs (07:08)
  • Re: comparing null value in plpgsql. Stephan Szabo (06:10)
  • comparing null value in plpgsql. Bhuvan A (05:18)
• 09 March 2002
  • Fwd: Bug in getTimestamp() of PostgreSQL JDBC driver? Peter T Mount (11:48)
• 08 March 2002
  • Re: Bug #608: cache lookup failed Juliano Ignacio (17:44)
  • Re: libpq not reentrant Bruce Momjian (01:09)
• 07 March 2002
  • Re: Bug #610: collation fails sorting because of strcoll() bug Tom Lane (21:21)
  • Bug #610: collation fails sorting because of strcoll() bug pgsql-bugs (19:36)
  • Bug #609: CREATE TABLE with implicit index should not fail if index already exists pgsql-bugs (17:27)
  • Re: Bug #608: cache lookup failed Laurent FAILLIE (16:36)
  • Re: Bug #608: cache lookup failed Tom Lane (16:08)
  • Re: Bug #608: cache lookup failed Laurent FAILLIE (16:00)
  • Re: regression - postgresql 7.2 on power pc/linux Stephan Szabo (15:44)
  • Re: Bug #608: cache lookup failed Tom Lane (15:05)
  • Re: Bug #608: cache lookup failed Laurent FAILLIE (10:47)
  • referential constraint bug Eric Lu (00:48)
• 06 March 2002
  • Re: Bug #608: cache lookup failed Tom Lane (18:35)
  • Bug #608: cache lookup failed pgsql-bugs (14:33)
  • regression - postgresql 7.2 on power pc/linux Arkadiusz Miskiewicz (09:18)
• 05 March 2002
  • JDBC Trouble when exception appears . Nicolas Paymal (09:56)
  • Re: postmaster problem.... Justin (02:57)
  • Re: Encoding Problem? Tatsuo Ishii (01:02)
• 04 March 2002
  • Re: Bug #607: to_date() function bug Tom Lane (21:54)
  • Re: BUG: bigint and indexes ? Stephan Szabo (21:00)
  • Bug #607: to_date() function bug pgsql-bugs (19:21)
  • Re: Sun Solaris 2.5.1 Seg Faults PostgreSQL7.1.3 build com Riendeau, Mike (19:13)
  • Re: Indexes not always used after inserts/updates/vacuum Reinhard Max (11:10)
  • Bug #606: exec sql ifdef, ... incorrect parsing pgsql-bugs (06:57)
  • Re: Make check problem with 7.2 Steven Núñez (05:44)
  • Re: Make check problem with 7.2 Bruce Momjian (05:03)
  • Re: Make check problem with 7.2 Steven Núñez (03:35)
  • Re: Make check problem with 7.2 Tom Lane (02:15)
  • Re: Make check problem with 7.2 Steven Núñez (01:03)
  • Re: Make check problem with 7.2 Steven Núñez (00:53)
• 03 March 2002
  • Re: Make check problem with 7.2 Tom Lane (20:36)
• 02 March 2002
  • Make check problem with 7.2 Steven Núñez (23:12)
  • Re: Large shared_buffers freezing computers Michael G. Martin (15:17)
  • We have visited your website shop.juni.gliwice.pl pgsql-bugs (10:51)
  • Large shared_buffers freezing computers Michael G. Martin (05:02)
  • Gmake check problem Steven Núñez (04:02)
• 01 March 2002
  • Re: Bug #605: timestamp(timestamp('a timestamp)) no longer works Andrew McMillan (23:56)
  • Re: SELECT statement causing terminating the backend Tom Lane (21:03)
  • Re: Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin (16:44)
  • Re: Bug #605: timestamp(timestamp('a timestamp)) no longer works Thomas Lockhart (15:16)
  • Re: Bug #605: timestamp(timestamp('a timestamp)) no longer works Tom Lane (15:03)
  • Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane (14:37)
  • BUG: bigint and indexes ? Victor Krasinsky (13:19)
  • Re: cannot install postgresql 7.2 UltraMax (12:38)
  • cannot install postgresql 7.2 UltraMax (10:27)
  • Bug #605: timestamp(timestamp('a timestamp)) no longer works pgsql-bugs (09:50)
  • about catalogue tables bugs? Fouad Fezzi (09:32)
  • Encoding Problem? cnliou (07:58)
  • Re: Indexes not always used after inserts/updates/vacuum Reinhard Max (07:06)
• 28 February 2002
  • Incorrect PostgreSQL 7.2 ODBC RPM for RedHat 6.2 Steve Wranovsky (18:49)
  • RSERV AND POSTGRESQL 7.2 free (16:00)
  • postmaster problem.... Nitesh (06:19)
• 27 February 2002
  • Segmentation Fault Sidney (23:09)
  • cannot install postgresql 7.2 UltraMax (14:04)
  • SELECT statement causing terminating the backend Radek Hrabčák (11:16)

• Thread Index
• [Prev Page]
• [Next Page]