• 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-02 Thread Index (1/2)

• Main Index
• [Prev Page]
• [Next Page]

• Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin (Thu 28 02:53)
• Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane (Thu 28 03:57)
• Re: Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin (Thu 28 04:15)
• Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane (Thu 28 04:28)
• Re: Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin (Thu 28 04:32)
• Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane (Thu 28 04:40)
• Re: Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin (Thu 28 04:45)
• Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane (Thu 28 05:00)
• Re: Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin (Thu 28 05:20)
• Re: Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin (Thu 28 14:40)
• Re: Indexes not always used after inserts/updates/vacuum analyze Michael G. Martin (Thu 28 04:41)
• Re: Indexes not always used after inserts/updates/vacuum Reinhard Max (Thu 28 11:56)
• Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane (Thu 28 14:51)
• Re: Indexes not always used after inserts/updates/vacuum Reinhard Max (Thu 28 15:00)
• Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane (Thu 28 15:16)
• Re: Indexes not always used after inserts/updates/vacuum Reinhard Max (Thu 28 16:43)
• Re: Indexes not always used after inserts/updates/vacuum analyze Tom Lane (Thu 28 21:10)
• performance problems on updates on large tables with indexes Reinhard Max (Wed 27 16:29)
• Re: performance problems on updates on large tables with indexes Tom Lane (Wed 27 21:42)
• function tree_level(varchar) (from OpenACS) no longer work under 7.2 Jean-Paul ARGUDO (Wed 27 08:07)
• Re: function tree_level(varchar) (from OpenACS) no longer work under 7.2 Tom Lane (Wed 27 15:07)
• Re: function tree_level(varchar) (from OpenACS) no longer work under 7.2 Jean-Paul ARGUDO (Wed 27 16:35)
• Re: JDBC/JSP: Strange Problem Josh Burdick (Tue 26 16:24)
• Bug #604: string join problem pgsql-bugs (Tue 26 13:50)
• Re: Bug #604: string join problem Tom Lane (Tue 26 15:35)
• Re: Bug #604: string join problem Erol Ozcan (Tue 26 16:22)
• Bug #603: time() problems with PostgreSQL 7.2 pgsql-bugs (Tue 26 13:43)
• Re: Bug #603: time() problems with PostgreSQL 7.2 Tom Lane (Tue 26 15:28)
• problems with configure connected with readline&history toxic (Tue 26 10:41)
• COPY FROM is not 8bit clean Darcy Buskermolen (Tue 26 04:19)
• <Possible follow-ups>
• COPY FROM is not 8bit clean Darcy Buskermolen (Tue 26 04:34)
• Re: COPY FROM is not 8bit clean Tom Lane (Tue 26 04:57)
• COPY FROM is not 8bit clean Darcy Buskermolen (Tue 26 04:42)
• Re: COPY FROM is not 8bit clean Tatsuo Ishii (Tue 26 12:17)
• Re: COPY FROM is not 8bit clean Darcy Buskermolen (Tue 26 16:20)
• Re: COPY FROM is not 8bit clean Tom Lane (Tue 26 17:48)
• Re: COPY FROM is not 8bit clean Darcy Buskermolen (Tue 26 16:27)
• Re: COPY FROM is not 8bit clean Bruce Momjian (Tue 26 18:05)
• Re: COPY FROM is not 8bit clean Tom Lane (Tue 26 23:33)
• Re: COPY FROM is not 8bit clean Bruce Momjian (Wed 27 03:09)
• Bug #602: Chinese characters query bug. pgsql-bugs (Mon 25 01:48)
• Re: Bug #602: Chinese characters query bug. Tatsuo Ishii (Mon 25 01:55)
• missing foreign key fails silently using COPY Lee Harr (Mon 25 01:11)
• Re: missing foreign key fails silently using COPY Tom Lane (Mon 25 17:24)
• Re: missing foreign key fails silently using COPY Tom Lane (Mon 25 18:55)
• Re: missing foreign key fails silently using COPY Tom Lane (Wed 27 23:04)
• Re: COPY when 'filename' is a directory Bruce Momjian (Sat 23 02:10)
• <Possible follow-ups>
• Re: COPY when 'filename' is a directory Bruce Momjian (Sat 23 21:46)
• Re: COPY when 'filename' is a directory Tom Lane (Sun 24 01:28)
• Re: COPY when 'filename' is a directory Brent Verner (Sun 24 01:56)
• Re: [PATCHES] COPY when 'filename' is a directory Tom Lane (Sun 24 02:11)
• Re: [PATCHES] COPY when 'filename' is a directory Bruce Momjian (Sun 24 02:31)
• Re: [PATCHES] COPY when 'filename' is a directory Tom Lane (Sun 24 02:41)
• Re: [PATCHES] COPY when 'filename' is a directory Bruce Momjian (Sun 24 02:47)
• Re: [PATCHES] COPY when 'filename' is a directory Tom Lane (Sun 24 03:19)
• Re: COPY when 'filename' is a directory Brent Verner (Sun 24 02:00)
• Re: [PATCHES] COPY when 'filename' is a directory Bruce Momjian (Sun 24 02:03)
• Re: Bug #534: factorial function Bruce Momjian (Sat 23 01:06)
• Bug #601: libpq needs a lo_truncate() or INV_TRUNC pgsql-bugs (Fri 22 23:07)
• Possible bug concerning LASTOID in 7.2 Coax (Fri 22 22:47)
• Re: Possible bug concerning LASTOID in 7.2 Tom Lane (Mon 25 23:29)
• CURRENT_TIMESTAMP not work correctly insinde a transaction. Nicolas Paymal (Fri 22 13:42)
• Re: CURRENT_TIMESTAMP not work correctly insinde a transaction. Thomas Lockhart (Fri 22 18:42)
• Re: CURRENT_TIMESTAMP not work correctly insinde a transaction. Peter Eisentraut (Fri 22 22:01)
• Re: CURRENT_TIMESTAMP not work correctly insinde a transaction. Tom Lane (Sat 23 00:36)
• Patch pgsql-7.2 AuthBlockSig Heiko Lehmann (Fri 22 10:53)
• Re: Patch pgsql-7.2 AuthBlockSig Bruce Momjian (Fri 22 15:38)
• Re: Patch pgsql-7.2 AuthBlockSig Tom Lane (Fri 22 15:59)
• Bug #600: how to run the Postgres postmaster with -i flag pgsql-bugs (Fri 22 08:24)
• Bug #599: ecpg does not parse correctly define and struct in the same file pgsql-bugs (Fri 22 05:23)
• [no subject] Hardeep (Thu 21 10:20)
• Full bug list Andy Marden (Thu 21 10:06)
• Re: Full bug list Justin (Fri 22 03:32)
• my pl/pgsql functions return weird results Olivier Garcia (Fri 22 08:17)
• Re: my pl/pgsql functions return weird results Tom Lane (Fri 22 15:10)
• <Possible follow-ups>
• Re: Full bug list Andy Marden (Fri 22 12:22)
• Re: Full bug list Justin (Tue 26 04:05)
• (plpgsql) DECLARE foo NUMERIC(5,2): syntax error at "(" Angus Lees (Thu 21 04:07)
• Re: (plpgsql) DECLARE foo NUMERIC(5,2): syntax error at "(" Tom Lane (Fri 22 00:08)
• Trying Cygwin version of PostgreSQL Peter (Wed 20 23:51)
• Re: Trying Cygwin version of PostgreSQL Tom Lane (Thu 21 03:24)
• Re: Trying Cygwin version of PostgreSQL Paul Rowland (Thu 21 12:37)
• Now trying Cygwin with normal download of PostgreSQL Peter (Fri 22 02:37)
• Re: Now trying Cygwin with normal download of PostgreSQL Tom Lane (Fri 22 15:29)
• <Possible follow-ups>
• Re: Trying Cygwin version of PostgreSQL Justin Clift (Fri 22 03:49)
• Trying Cygwin version of PostgreSQL again Peter (Fri 22 05:44)
• Re: Trying Cygwin version of PostgreSQL again Justin Clift (Fri 22 06:12)
• Re: Trying Cygwin version of PostgreSQL again Justin (Tue 26 04:13)
• Bug #598: optimizer: convert 'IN' to join pgsql-bugs (Wed 20 21:29)
• Re: Dates and year 2000 Andy Marden (Wed 20 21:10)
• Re: Dates and year 2000 Tom Lane (Wed 20 23:21)
• Re: Dates and year 2000 Andy Marden (Thu 21 08:03)
• Re: Dates and year 2000 Andy Marden (Thu 21 09:40)
• Re: Dates and year 2000 Thomas Lockhart (Thu 21 14:13)
• Re: Dates and year 2000 Thomas Lockhart (Thu 21 01:54)
• schema error upgrading from 7.1 to 7.2 Vivek Khera (Wed 20 21:00)
• Re: [GENERAL] schema error upgrading from 7.1 to 7.2 Tom Lane (Wed 20 21:31)
• Re: [GENERAL] schema error upgrading from 7.1 to 7.2 Vivek Khera (Wed 20 21:41)
• Re: [GENERAL] schema error upgrading from 7.1 to 7.2 Tom Lane (Wed 20 23:18)
• Re: [GENERAL] schema error upgrading from 7.1 to 7.2 Vivek Khera (Thu 21 14:36)
• Bug #597: ResultSet.next() throws NullPointerException pgsql-bugs (Wed 20 01:20)
• Re: Bug #597: ResultSet.next() throws NullPointerException Bruce Momjian (Fri 22 05:44)
• Re: Bug #597: ResultSet.next() throws NullPointerException Bruce Momjian (Sat 23 02:38)
• Bug #596: bind to 127.0.0.1 in pgstat.c in secure server pgsql-bugs (Tue 19 22:36)
• Postgresql 7.1.3 not thread safe Alain Picard (Tue 19 01:24)
• Postgresql 7.1.3 not thread safe Alain Picard (Tue 19 05:51)
• Re: Postgresql 7.1.3 not thread safe Tom Lane (Tue 19 21:36)
• Re: Postgresql 7.1.3 not thread safe Alain Picard (Wed 20 00:32)
• 7.2 contrib RPM broken Greg Johnson (Mon 18 22:09)
• ecpg did not precompile declare cursor Bernhard Rückerl (Mon 18 21:54)
• ecpg did not precompile declare cursor Lee Kindness (Wed 20 09:21)
• Bug #595: No connection with jdbc since update to 7.2 pgsql-bugs (Mon 18 13:30)
• Bug #594: postgresql-odbc-7.2-1PGDG.i386.rpm lacks the actual shared library pgsql-bugs (Mon 18 11:51)
• Bug #593: postgresql-odbc-7.2-1PGDG.i386.rpm lacks the actual shared library pgsql-bugs (Mon 18 11:41)
• Bug #592: postgresql-odbc-7.2-1PGDG.i386.rpm lacks the actual shared library pgsql-bugs (Mon 18 11:35)
• crash on cash_words('21,474,836.48'::money) Eugene Pervago (Sun 17 21:45)
• Re: crash on cash_words('21,474,836.48'::money) Tom Lane (Tue 19 22:21)
• Bug #591: Postgres apparently not identifying users created in Caps pgsql-bugs (Sat 16 18:22)
• Re: Bug #591: Postgres apparently not identifying users created in Caps Tom Lane (Sat 16 18:47)
• psqlODBC Marc Breneiser (Sat 16 16:30)
• Possible Bug Chuck Handshy (Fri 15 22:25)
• Re: Possible Bug Tom Lane (Tue 19 20:34)
• Postgres 7.1 problem Ed Erdman (Fri 15 20:20)
• rename column and trigger on column Chris Sutton (Fri 15 17:42)
• Compiling error Torres Abarca Jaime (Fri 15 16:44)
• Re: Compiling error Tom Lane (Tue 19 20:25)
• Bug with SQL-COPY in 7.2 Detlef Plotzky (Fri 15 14:07)
• Bug #590: Migration to Postgres 7.2 impossible when capitals are used in database name pgsql-bugs (Fri 15 12:06)
• Re: Bug #590: Migration to Postgres 7.2 impossible when capitals are used in database name Tom Lane (Fri 15 15:22)
• Bug #589: JDBC KEY_SEQ in getImportedKey starts at 0 pgsql-bugs (Fri 15 11:51)
• (JDBC) KEY_SEQ in Foreign Key result set starts at 0, should be 1 David Goodenough (Fri 15 11:46)
• Bug in Postrgresql 7.2 migrating from 7.1.3 Ruud van den Brink (Fri 15 11:45)
• bugs Srinivasa R Chava (Thu 14 15:16)
• Re: bugs Tom Lane (Tue 19 20:22)
• Bug #588: Postgresql will not build on AIX; cannot locate tcl library pgsql-bugs (Wed 13 22:10)
• Bug #587: Postgresql will not build on HP-UX 11.0 in debug mode pgsql-bugs (Wed 13 21:09)
• Re: Bug #587: Postgresql will not build on HP-UX 11.0 in Peter Eisentraut (Wed 13 21:43)
• Re: Bug #587: Postgresql will not build on HP-UX 11.0 in debug mode Tom Lane (Wed 13 22:08)
• BLOB support is broken in the 7.2/7.3 JDBC driver, works in 7.1 driver Marc Lavergne (Wed 13 07:11)
• [Fwd: BLOB support is broken in the 7.2/7.3 JDBC driver, works in 7.1 driver java.sql.SQLException: ERROR: oidin: error in "\377\330\377\340... I'm on Linux 2.4.16 using JDK 1.4.0 but it fails in 1.3.1 as well. Here's a quick reproducible test case: -- start -- package sample.java.jdbc; import java.sql.*; import java.io.*; import java.util.*; class testBlob { public static void main(String args[]) { new testBlob(); System.exit(0); } public testBlob() { System.out.println("Let's begin the test ..."); String v_username = "postgre"; String v_password = "postgre"; String v_database = "jdbc:postgresql://127.0.0.1/TEST"; PreparedStatement v_pstmt = null; try { DriverManager.registerDriver(new org.postgresql.Driver()); Connection v_conn = DriverManager.getConnection( v_database, v_username, v_password); v_conn.setAutoCommit(false); File v_file = new File("/home/postgre/someth! ing.jpg"); FileInputStream v_fis = new FileInputStream(v_file); v_pstmt = v_conn.prepareStatement( "insert into lob_test (id,data) values (?,?)"); v_pstmt.setInt(1,2); v_pstmt.setBinaryStream(2,v_fis,(int)v_file.length()); System.out.println("now you see me"); v_pstmt.executeUpdate(); System.out.println("now you don't"); v_conn.commit(); v_fis.close(); v_pstmt.close(); } catch (IOException e_io) { System.out.println(e_io); } catch (SQLException e_sql) { System.out.println(e_sql); } System.out.println("You'll only get here with the 7.1 driver!"); } } -- end -- 01010101010101010101010101010101010101010101010101 Marc P. Lavergne [wk:407-648-6996] Product Development richLAVA Corporation -- "Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had v! ery little chance of reading a document written on another computer, a Marc Lavergne (Wed 13 07:07)
• BLOB support is broken in the 7.2/7.3 JDBC driver, works in 7.1 driver java.sql.SQLException: ERROR: oidin: error in "\377\330\377\340... I'm on Linux 2.4.16 using JDK 1.4.0 but it fails in 1.3.1 as well. Here's a quick reproducible test case: -- start -- package sample.java.jdbc; import java.sql.*; import java.io.*; import java.util.*; class testBlob { public static void main(String args[]) { new testBlob(); System.exit(0); } public testBlob() { System.out.println("Let's begin the test ..."); String v_username = "postgre"; String v_password = "postgre"; String v_database = "jdbc:postgresql://127.0.0.1/TEST"; PreparedStatement v_pstmt = null; try { DriverManager.registerDriver(new org.postgresql.Driver()); Connection v_conn = DriverManager.getConnection( v_database, v_username, v_password); v_conn.setAutoCommit(false); File v_file = new File("/home/postgre/something.jpg"); FileInputStream v_fis = new FileInputStream(v_file); v_pstmt = v_conn.prepareStatement( "insert into lob_test (id,data) values (?,?)"); v_pstmt.setInt(1,2); v_pstmt.setBinaryStream(2,v_fis,(int)v_file.length()); System.out.println("now you see me"); v_pstmt.executeUpdate(); System.out.println("now you don't"); v_conn.commit(); v_fis.close(); v_pstmt.close(); } catch (IOException e_io) { System.out.println(e_io); } catch (SQLException e_sql) { System.out.println(e_sql); } System.out.println("You'll only get here with the 7.1 driver!"); } } -- end -- 01010101010101010101010101010101010101010101010101 Marc P. Lavergne [wk:407-648-6996] Product Development richLAVA Corporation -- "Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of reading a document written on another computer, another word processor, or another network." -Tim Berners-Lee (Technology Review, July 1996) 01010101010101010101010101010101010101010101010101 -- 01010101010101010101010101010101010101010101010101 Marc P. Lavergne [wk:407-648-6996] Product Development richLAVA Corporation -- "Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of reading a document written on another computer, another word processor, or another network." -Tim Berners-Lee (Technology Review, July 1996) java.sql.SQLException: ERROR: oidin: error in "\377\330\377\340... I'm on Linux 2.4.16 using JDK 1.4.0 but it fails in 1.3.1 as well. Here's a quick reproducible test case: -- start -- package sample.java.jdbc; import java.sql.*; import java.io.*; import java.util.*; class testBlob { public static void main(String args[]) { new testBlob(); System.exit(0); } public testBlob() { System.out.println("Let's begin the test ..."); String v_username = "postgre"; String v_password = "postgre"; String v_database = "jdbc:postgresql://127.0.0.1/TEST"; PreparedStatement v_pstmt = null; try { DriverManager.registerDriver(new org.postgresql.Driver()); Connection v_conn = DriverManager.getConnection( v_database, v_username, v_password); v_conn.setAutoCommit(false); File v_file = new File("/home/postgre/something.jpg"); FileInputStream v_fis = new FileInputStream(v_file); v_pstmt = v_conn.prepareStatement( "insert into lob_test (id,data) values (?,?)"); v_pstmt.setInt(1,2); v_pstmt.setBinaryStream(2,v_fis,(int)v_file.length()); System.out.println("now you see me"); v_pstmt.executeUpdate(); System.out.println("now you don't"); v_conn.commit(); v_fis.close(); v_pstmt.close(); } catch (IOException e_io) { System.out.println(e_io); } catch (SQLException e_sql) { System.out.println(e_sql); } System.out.println("You'll only get here with the 7.1 driver!"); } } -- end -- 01010101010101010101010101010101010101010101010101 Marc P. Lavergne [wk:407-648-6996] Product Development richLAVA Corporation -- "Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of reading a document written on another computer, another word processor, or another network." -Tim Berners-Lee (Technology Review, July 1996) 01010101010101010101010101010101010101010101010101 -- 01010101010101010101010101010101010101010101010101 Marc P. Lavergne [wk:407-648-6996] Product Development richLAVA Corporation -- "Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of reading a document written on another computer, another word processor, or another network." -Tim Berners-Lee (Technology Review, July 1996) Marc Lavergne (Wed 13 06:46)
• createdb problem Isamary García (Tue 12 20:10)
• Bug #584: postgresql will not build on Solaris with cc pgsql-bugs (Tue 12 19:27)
• Re: Bug #584: postgresql will not build on Solaris with cc Tom Lane (Tue 12 21:15)
• Re: Bug #584: postgresql will not build on Solaris with cc Nishad Prakash (Tue 12 22:10)
• <Possible follow-ups>
• Bug #584: postgresql will not build on Solaris with cc pgsql-bugs (Tue 12 19:34)
• Bug #584: postgresql will not build on Solaris with cc pgsql-bugs (Tue 12 19:54)
• Bug #583: Wrong example in 7.2 Tutorial pgsql-bugs (Tue 12 18:55)
• Re: Bug #583: Wrong example in 7.2 Tutorial Bruce Momjian (Tue 12 22:26)
• Bug #582: no mapping for java.sql.Types.DECIMAL pgsql-bugs (Tue 12 01:38)
• Bug #581: Sequence cannot be deleted pgsql-bugs (Tue 12 01:26)
• Re: Bug #581: Sequence cannot be deleted Stephan Szabo (Tue 12 02:14)
• Re: Bug #581: Sequence cannot be deleted Tom Lane (Tue 12 02:17)
• Initdb Hangs Blossom, Eric (Tue 12 00:05)
• Re: Initdb Hangs Tom Lane (Mon 18 17:39)
• <Possible follow-ups>
• Re: Initdb Hangs Blossom, Eric (Tue 12 00:14)
• Bug #580: Optimizer uses seq scan only pgsql-bugs (Mon 11 22:51)
• Re: Bug #580: Optimizer uses seq scan only Tom Lane (Mon 11 23:22)
• Re: Bug #580: Optimizer uses seq scan only Stephan Szabo (Mon 11 23:44)
• Re: Bug #578: pg_dumpall from 7.1.3 can not be imported in 7.2.0 Tom Lane (Mon 11 19:47)
• Bug #579: Auto-VACUUM doesnt work pgsql-bugs (Mon 11 07:47)
• Re: Bug #579: Auto-VACUUM doesnt work Tom Lane (Mon 11 16:07)
• Re: Bug #579: Auto-VACUUM doesnt work Peter Eisentraut (Mon 11 16:11)
• Bug #578: pg_dumpall from 7.1.3 can not be imported in 7.2.0 pgsql-bugs (Fri 08 19:03)
• Re: Bug #578: pg_dumpall from 7.1.3 can not be imported in Stephan Szabo (Fri 08 19:34)
• Re: Bug #578: pg_dumpall from 7.1.3 can not be imported in Rainer Tammer (Sat 09 06:59)
• Re: Bug #578: pg_dumpall from 7.1.3 can not be imported in 7.2.0 Tom Lane (Sun 10 23:50)
• Bug #577: incorect sort using order by pgsql-bugs (Fri 08 07:25)
• Re: Bug #577: incorect sort using order by Tom Lane (Fri 08 16:10)
• Bug #576: Can not compile IRIX + GCC pgsql-bugs (Fri 08 04:35)
• Re: Bug #576: Can not compile IRIX + GCC Bruce Momjian (Fri 08 04:53)
• Re: Bug #576: Can not compile IRIX + GCC Luis Amigo (Fri 08 09:27)
• Bug #575: Build Problem with Postgresql 7.1.3 on Aix 4.3.3 with VisualAge 5.0 compiler resources: pgsql-bugs (Thu 07 15:17)
• Re: Bug #575: Build Problem with Postgresql 7.1.3 on Aix 4.3.3 with VisualAge 5.0 compiler resources: Tom Lane (Thu 07 17:34)
• Bug #574: can not create tables that start with "Clinic" pgsql-bugs (Thu 07 00:00)
• Re: Bug #574: can not create tables that start with "Clinic" Peter Eisentraut (Thu 07 00:18)
• Re: Bug #574: can not create tables that start with "Clinic" Edwin Grubbs (Thu 07 00:24)
• index and timestamp column Thomas Zehetbauer (Tue 05 17:25)
• Re: [CYGWIN] resource leak in 7.2 Henshall, Stuart - WCP (Tue 05 16:53)
• Re: [CYGWIN] resource leak in 7.2 Tom Lane (Tue 05 17:12)

---

• Main Index
• [Prev Page]
• [Next Page]

---

Mail converted by MHonArc