pgsql-bugs since 2011-03-15 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)

Browse Archives

Prev | Next

March 15, 2011

Thread Author Time
BUG #5928: PD_ALL_VISIBLE flag incorrectly set warning messages Lane Stevens 00:01
Re: BUG #5928: PD_ALL_VISIBLE flag incorrectly set warning messages Heikki Linnakangas 06:03
BUG #5929: ERROR: found toasted toast chunk for toast value 260340218 in pg_toast_260339342 Tambet Matiisen 09:28
BUG #5930: Increasing log level to debug5 database not working thiruppathi 11:20
Re: BUG #5930: Increasing log level to debug5 database not working Kevin Grittner 14:02
BUG #5931: password when setup mac 14:23
SELECT '(1, nan, 3)'::cube Robert Brewer 15:57
SELECT '(1, nan, 3)'::cube; Robert Brewer 16:08
Re: SELECT '(1, nan, 3)'::cube; Tom Lane 17:07
Re: BUG #5929: ERROR: found toasted toast chunk for toast value 260340218 in pg_toast_260339342 Kevin Grittner 17:47
Re: SELECT '(1, nan, 3)'::cube; Robert Brewer 17:54
Re: SELECT '(1, nan, 3)'::cube; Tom Lane 18:43
BUG #5932: CLUSTER doesn't update n_dead_tup Andy Lester 22:23

March 16, 2011

Thread Author Time
BUG #5933: database restore error rajesh 07:10
Re: BUG #5929: ERROR: found toasted toast chunk for toast value 260340218 in pg_toast_260339342 Tambet Matiisen 11:10
Re: BUG #5929: ERROR: found toasted toast chunk for toast value 260340218 in pg_toast_260339342 Kevin Grittner 15:09
Re: BUG #5933: database restore error Kevin Grittner 15:14
BUG #5934: postgresql.conf: optional equal sign Frederic Junod 15:25
Re: SELECT '(1, nan, 3)'::cube; bricklen 16:18
Re: SELECT '(1, nan, 3)'::cube; Robert Brewer 18:14
Re: BUG #5929: ERROR: found toasted toast chunk for toast value 260340218 in pg_toast_260339342 Tambet Matiisen 19:08
Re: BUG #5929: ERROR: found toasted toast chunk for toast value 260340218 in pg_toast_260339342 Kevin Grittner 20:29
Re: BUG #5934: postgresql.conf: optional equal sign Euler Taveira de Oliveira 23:07

March 17, 2011

Thread Author Time
Re: Re: [BUGS] BUG #5842: Memory leak in PL/Python when taking slices of results Robert Haas 02:40
Re: BUG #5934: postgresql.conf: optional equal sign Frederic Junod 07:58
Re: BUG #5929: ERROR: found toasted toast chunk for toast value 260340218 in pg_toast_260339342 Tambet Matiisen 08:07
Re: Re: [BUGS] BUG #5842: Memory leak in PL/Python when taking slices of results Marko Kreen 15:01
Re: Re: [BUGS] BUG #5842: Memory leak in PL/Python when taking slices of results Alvaro Herrera 15:15
Re: BUG #5842: Memory leak in PL/Python when taking slices of results Alvaro Herrera 18:31
BUG #5935: Log lotation not working for default log format Brad Nicholson 19:36
Re: BUG #5935: Log lotation not working for default log format Korry Douglas 20:00
Re: BUG #5935: Log lotation not working for default log format Nicholson, Brad (Toronto, ON, CA) 20:16
Re: BUG #5935: Log lotation not working for default log format Korry Douglas 20:52

March 18, 2011

Thread Author Time
Setting timezone: is it bug or intended? Yura Sokolov 08:22
TO_CHAR(timestamptz,datetimeformat) wrong after DST change Jonathan Brinkman 14:55
Re: TO_CHAR(timestamptz,datetimeformat) wrong after DST change Tom Lane 15:41
Re: TO_CHAR(timestamptz,datetimeformat) wrong after DST change Jonathan Brinkman 16:01
Re: TO_CHAR(timestamptz,datetimeformat) wrong after DST change Kevin Grittner 16:33
Re: TO_CHAR(timestamptz,datetimeformat) wrong after DST change Tom Lane 16:46

March 19, 2011

Thread Author Time
Re: Problem with ALTER TABLE - occasional "tuple concurrently updated" Robert Haas 02:12
BUG #5936: Cannot connect to Server Srikanth 05:56
Re: BUG #5936: Cannot connect to Server tomas 21:17

March 21, 2011

Thread Author Time
BUG #5937: initdb: FATAL error: could not open relation with OID 2608 Etienne Robillard 11:51
Re: Setting timezone: is it bug or intended? Susanne Ebrecht 12:51
Re: BUG #5931: password when setup Susanne Ebrecht 12:56
Re: BUG #5931: password when setup Harald Armin Massa 13:02
Re: TO_CHAR(timestamptz,datetimeformat) wrong after DST change Jonathan Brinkman 13:13
Re: TO_CHAR(timestamptz,datetimeformat) wrong after DST change Jonathan Brinkman 13:24
Re: BUG #5937: initdb: FATAL error: could not open relation with OID 2608 Tom Lane 15:00
Re: BUG #5937: initdb: FATAL error: could not open relation with OID 2608 Etienne Robillard 15:29
Re: TO_CHAR(timestamptz,datetimeformat) wrong after DST change Robert Haas 15:49
Warm Standby startup process unconditionally hangs Bernd Helmle 16:44

March 22, 2011

Thread Author Time
BUG #5938: PostgreSQL Installer outputs log file with superuser password in clear text Craig Sacco 05:10
BUG #5939: About bytea Vincent Chan 06:34
Re: BUG #5800: "corrupted" error messages (encoding problem ?) genamiga 07:07
BUG #5940: Creating a foreign key on an empty table locks table Adriaan 09:50
Re: TO_CHAR(timestamptz,datetimeformat) wrong after DST change Jonathan Brinkman 12:56
Re: BUG #5937: initdb: FATAL error: could not open relation with OID 2608 Alvaro Herrera 14:51
Bug with STABLE function using the wrong snapshot (probably during planning) Matthijs Bomhoff 15:31
Re: BUG #5938: PostgreSQL Installer outputs log file with superuser password in clear text Dave Page 15:45
Re: BUG #5938: PostgreSQL Installer outputs log file with superuser password in clear text Dave Page 16:09
Re: BUG #5938: PostgreSQL Installer outputs log file with superuser password in clear text Simon Riggs 16:33
BUG #5941: i don t understand GIMENEZ alex 19:39
Re: BUG #5941: i don t understand Devrim GÜNDÜZ 19:43
Re: BUG #5938: PostgreSQL Installer outputs log file with superuser password in clear text Robert Haas 19:57
Re: BUG #5941: i don t understand Robert Haas 19:58
psql crashes with bad history file in 9.0.3 Josh Berkus 20:40
Re: psql crashes with bad history file in 9.0.3 John R Pierce 20:56
Re: BUG #5937: initdb: FATAL error: could not open relation with OID 2608 Etienne Robillard 22:23
Re: BUG #5937: initdb: FATAL error: could not open relation with OID 2608 Tom Lane 22:26
Re: BUG #5937: initdb: FATAL error: could not open relation with OID 2608 Etienne Robillard 22:48
Re: Setting timezone: is it bug or intended? Yura Sokolov 22:52
ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP Kasia Tuszynska 23:05

March 23, 2011

Thread Author Time
Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP Tatsuo Ishii 01:58
Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP Itagaki Takahiro 01:58
Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP Itagaki Takahiro 03:38
Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP Tatsuo Ishii 04:02
Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP Itagaki Takahiro 04:16
Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP Tatsuo Ishii 05:16
Re: postgres 9 streaming replication Alex Lai 12:07
Index Ignored Due To Use Of View Donald Fraser 12:50
Re: Index Ignored Due To Use Of View Donald Fraser 13:10
Re: Index Ignored Due To Use Of View Merlin Moncure 13:54
BUG #5942: pg_trgm.sql has cyclic dependency on type gtrgm creation Arthur Nascimento 19:09
Re: TO_CHAR(timestamptz,datetimeformat) wrong after DST change Susanne Ebrecht 19:33
Re: Warm Standby startup process unconditionally hangs 📎 Simon Riggs 20:37
Re: Warm Standby startup process unconditionally hangs Alvaro Herrera 21:33
Re: BUG #5942: pg_trgm.sql has cyclic dependency on type gtrgm creation Tom Lane 22:47
BUG #5943: jdbc client doesn't omit pg_toast_temp tables from schema views Daniel Ceregatti 23:01
BUG #5944: COPY FROM doesn't work with international characters Nathan Davalos 23:32
Re: BUG #5944: COPY FROM doesn't work with international characters John R Pierce 23:49

March 24, 2011

Thread Author Time
Re: Index Ignored Due To Use Of View Tom Lane 00:07
Re: BUG #5944: COPY FROM doesn't work with international characters Nathan M. Davalos 00:33
Re: BUG #5944: COPY FROM doesn't work with international characters John R Pierce 00:54
Re: BUG #5944: COPY FROM doesn't work with international characters Nathan M. Davalos 00:59
Service Wont Start Viner, Adrian 09:12
Re: BUG #5938: PostgreSQL Installer outputs log file with superuser password in clear text Dave Page 09:12
Re: postgres 9 streaming replication Fujii Masao 12:13
Re: Can't use WITH in a PERFORM query in PL/pgSQL? depstein 15:21
Re: Can't use WITH in a PERFORM query in PL/pgSQL? Pavel Stehule 15:36
Re: BUG #5944: COPY FROM doesn't work with international characters Nathan M. Davalos 15:48
Re: Can't use WITH in a PERFORM query in PL/pgSQL? Merlin Moncure 15:54
Re: Service Wont Start Heikki Linnakangas 18:08
Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP Kasia Tuszynska 18:33
Re: BUG #5944: COPY FROM doesn't work with international characters Josh Berkus 18:53
Re: BUG #5943: jdbc client doesn't omit pg_toast_temp tables from schema views Kris Jurka 20:32

March 25, 2011

Thread Author Time
Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP Itagaki Takahiro 01:44
Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP Tatsuo Ishii 02:24
BUG #5945: serial repetition Error! shenwenguang 08:26
BUG #5946: Long exclusive lock taken by vacuum (not full) Maxim Boguk 08:56
BUG #5947: Error while running query Raman Sharma 09:47
BUG #5948: JDBC wrond insert of timestamp data yuriy.tereschuk 10:58
Re: BUG #5947: Error while running query Greg Stark 11:46
BUG #5949: ODBC driver. Binding Arrays of Parameters Mihail Popov 13:35
BUG #5950: backend terminating after altering table alex 13:37
Re: BUG #5939: About bytea Peter Eisentraut 14:00
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Alvaro Herrera 14:16
Re: BUG #5948: JDBC wrond insert of timestamp data Kris Jurka 15:00
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Tom Lane 15:17
checking on bug #5917 Jim Woodworth 15:27
Re: BUG #5950: backend terminating after altering table Tom Lane 15:30
Re: postgres 9 streaming replication Alex Lai 15:34
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Christopher Browne 15:58
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Tom Lane 16:10
Re: checking on bug #5917 Tom Lane 16:16
Re: checking on bug #5917 Devrim GÜNDÜZ 17:04
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Alvaro Herrera 19:26
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Tom Lane 19:43
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Greg Stark 20:26
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Tom Lane 20:48
BUG #5951: ERRO NO INICIO DA INSTALACAO DIEGO BALAN 20:59
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Greg Stark 21:09
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Tom Lane 21:34
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Maxim Boguk 21:43
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Christopher Browne 21:46
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Tom Lane 21:56

March 26, 2011

Thread Author Time
BUG #5952: SetRWConflict assertion failure YAMAMOTO Takashi 03:26
BUG #5953: pgadmin sql-query text pad doesn't work martin van leeuwen 21:55
Re: checking on bug #5917 Robert Haas 22:08

March 27, 2011

Thread Author Time
Re: BUG #5951: ERRO NO INICIO DA INSTALACAO Euler Taveira de Oliveira 14:07
Re: BUG #5953: pgadmin sql-query text pad doesn't work Kevin Grittner 18:23
Re: BUG #5952: SetRWConflict assertion failure 📎 Kevin Grittner 19:18

March 28, 2011

Thread Author Time
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Robert Haas 04:25
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Robert Haas 04:28
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Tom Lane 04:29
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Alvaro Herrera 10:26
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Alvaro Herrera 14:03
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Alvaro Herrera 14:05
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Rainer Pruy 14:28
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Rainer Pruy 14:31
Re: BUG #5950: backend terminating after altering table Sergey Burladyan 18:04
Re: BUG #5950: backend terminating after altering table Tom Lane 18:15
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Robert Haas 18:20
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Christopher Browne 19:01
BUG #5955: One-click installer does not escape password Rob Grant 19:07
Re: BUG #5950: backend terminating after altering table Tom Lane 19:47
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Tom Lane 20:01
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Christopher Browne 20:21
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Jan Wieck 23:55

March 29, 2011

Thread Author Time
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Tom Lane 00:07
Re: BUG #5946: Long exclusive lock taken by vacuum (not full) Jan Wieck 00:48
Re: BUG #5927: PostgreSQL8.2 Craig Ringer 02:22
BUG #5956: quiero crear una base de datos -E LATIN1 en la version 8.4 Mario Barrientos 22:53

March 30, 2011

Thread Author Time
BUG #5957: createdb with description and md5 auth forces to provide password twice Grzegorz Szpetkowski 01:20
BUG #5958: Connection error when authentication is kerberos jack liu 02:58
BUG #5959: pg_restore --use-list does not always work with a pg_restore generated TOC file Per-Olov Esgard 10:39
Re: [GENERAL] postgresql-8.4 error fhaegele 11:57
Re: [GENERAL] postgresql-8.4 error -> BUG fhaegele 12:03
Re: BUG #5945: serial repetition Error! Joshua Tolley 12:57
BUG #5960: No rule to make target 'libpq.a', needed by 'all-static-lib' Julia Jacobson 13:54
Postgres not using indexes Lawrence Cohan 15:00
Re: BUG #5960: No rule to make target 'libpq.a', needed by 'all-static-lib' Etienne Robillard 15:14
Re: Postgres not using indexes Nathan M. Davalos 16:04
Re: Postgres not using indexes Pavel Stehule 16:07
Re: Postgres not using indexes Lawrence Cohan 16:13
Re: Postgres not using indexes Kevin Grittner 16:45
Re: Postgres not using indexes 📎 Lawrence Cohan 16:51
Re: Postgres not using indexes Lawrence Cohan 16:53
Re: BUG #5960: No rule to make target 'libpq.a', needed by 'all-static-lib' julia.jacobson 16:56
Re: Postgres not using indexes Kevin Grittner 17:32
backend for database 'A' crashes/is killed -> corrupt index in database 'B' Jon Nelson 18:06
Re: Postgres not using indexes 📎 Lawrence Cohan 18:32
Re: Postgres not using indexes Kevin Grittner 18:51
Re: Postgres not using indexes Lawrence Cohan 19:05
Re: Postgres not using indexes Harry Rossignol 19:45
Re: Postgres not using indexes Kevin Grittner 19:49
Re: Postgres not using indexes Kevin Grittner 20:11
Re: Postgres not using indexes Lawrence Cohan 20:49
Re: BUG #5960: No rule to make target 'libpq.a', needed by 'all-static-lib' Julia Jacobson 21:44

March 31, 2011

Thread Author Time
Re: backend for database 'A' crashes/is killed -> corrupt index in database 'B' Heikki Linnakangas 07:58
Re: BUG #5856: pg_attribute.attinhcount is not correct. Noah Misch 10:06
Re: backend for database 'A' crashes/is killed -> corrupt index in database 'B' Jon Nelson 11:41
Re: BUG #5856: pg_attribute.attinhcount is not correct. Bernd Helmle 12:35
BUG #5961: JDBC Driver acceptURL does not check 'jdbc:postgresql:' Martin Handsteiner 13:09
Re: [GENERAL] postgresql-8.4 error fhaegele 13:44
Re: BUG #5961: JDBC Driver acceptURL does not check 'jdbc:postgresql:' Kris Jurka 15:11
Re: BUG #5856: pg_attribute.attinhcount is not correct. Robert Haas 15:11
Re: Postgres not using indexes Greg Stark 17:28
Re: BUG #5961: JDBC Driver acceptURL does not check 'jdbc:postgresql:' 📎 Kris Jurka 19:45
Re: Postgres not using indexes Kevin Grittner 22:33

Browse Archives

Prev | Next