Postgresql General Discussion

• Thread Index

• Re: psql connection via localhost or 127.0.0.1
  • From: Edoardo Panfili
• Re: psql connection via localhost or 127.0.0.1
  • From: Adrian Klaver
• Re: psql connection via localhost or 127.0.0.1
  • From: Edoardo Panfili
• Re: psql connection via localhost or 127.0.0.1
  • From: Adrian Klaver
• Re: psql connection via localhost or 127.0.0.1
  • From: Edoardo Panfili
• Re: psql connection via localhost or 127.0.0.1
  • From: Edoardo Panfili
• Re: psql connection via localhost or 127.0.0.1
  • From: John R Pierce
• Re: psql connection via localhost or 127.0.0.1
  • From: Edoardo Panfili
• Re: psql connection via localhost or 127.0.0.1
  • From: Adrian Klaver
• Re: psql connection via localhost or 127.0.0.1
  • From: Tom Lane
• Re: psql connection via localhost or 127.0.0.1
  • From: John R Pierce
• Re: Performance of UPDATE SET = FROM vs UPDATE SET = (SELECT ...)
  • From: Shaun Thomas
• Re: psql connection via localhost or 127.0.0.1
  • From: Adrian Klaver
• psql connection via localhost or 127.0.0.1
  • From: Edoardo Panfili
• Re: DATA corruption after promoting slave to master
  • From: Shaun Thomas
• Re: Performance problem on 2 PG versions on same query
  • From: Rémy-Christophe Schermesser
• Re: Incomplete startup packet help needed
  • From: Francisco Olarte
• PLV8 and JS exports / referencing
  • From: Jon Erdman
• Re: Performance problem on 2 PG versions on same query
  • From: Tom Lane
• Re: Performance problem on 2 PG versions on same query
  • From: Tomas Vondra
• Re: Performance problem on 2 PG versions on same query
  • From: Tom Lane
• Re: Performance problem on 2 PG versions on same query
  • From: Tomas Vondra
• Performance problem on 2 PG versions on same query
  • From: Rémy-Christophe Schermesser
• Re: Re: [BUGS] [HACKERS] COPY TO returning empty result with parallel ALTER TABLE
  • From: Bernd Helmle
• Re: Re: [BUGS] [HACKERS] COPY TO returning empty result with parallel ALTER TABLE
  • From: Tom Lane
• Re: Incomplete startup packet help needed
  • From: memtec
• Re: Tablespace limit feature
  • From: Alvaro Herrera
• Re: [BUGS] [HACKERS] COPY TO returning empty result with parallel ALTER TABLE
  • From: Andres Freund
• Re: [HACKERS] COPY TO returning empty result with parallel ALTER TABLE
  • From: Sven Wegener
• Re: [HACKERS] COPY TO returning empty result with parallel ALTER TABLE
  • From: Sven Wegener
• Re: [HACKERS] COPY TO returning empty result with parallel ALTER TABLE
  • From: Andrew Dunstan
• Re: Tablespace limit feature
  • From: Alejandro Carrillo
• Re: [HACKERS] COPY TO returning empty result with parallel ALTER TABLE
  • From: Tom Lane
• Re: [HACKERS] COPY TO returning empty result with parallel ALTER TABLE
  • From: Bernd Helmle
• Re: Tablespace limit feature
  • From: Stephen Frost
• Re: Tablespace limit feature
  • From: John R Pierce
• Re: Tablespace limit feature
  • From: Stephen Frost
• Re: Tablespace limit feature
  • From: Rob Sargent
• Re: Tablespace limit feature
  • From: David W Noon
• Re: Tablespace limit feature
  • From: Guillaume Lelarge
• Re: Tablespace limit feature
  • From: Guillaume Lelarge
• Re: Tablespace limit feature
  • From: Alejandro Carrillo
• Re: Tablespace limit feature
  • From: Stephen Frost
• Re: Tablespace limit feature
  • From: Guillaume Lelarge
• Re: Tablespace limit feature
  • From: Stephen Frost
• Re: Tablespace limit feature
  • From: Adrian Klaver
• Tablespace limit feature
  • From: Alejandro Carrillo
• Is any information about trigger-name and src-table available at the protocol-level?
  • From: Andreas Joseph Krogh
• Re: STABLE vs. IMMUTABLE w.r.t. indexes
  • From: Moshe Jacobson
• Re: Help with PostgreSQL 9.4 to expand jsonb int array into table with row numbers
  • From: hari . fuchs
• Re: Help with PostgreSQL 9.4 to expand jsonb int array into table with row numbers
  • From: David G Johnston
• Re: Is it possible to set a timeout for optimization in PostgreSQL?
  • From: Andreas Kretschmer
• Is it possible to set a timeout for optimization in PostgreSQL?
  • From: Zhan Li
• Dynomite from Netflix - Making Non-Distributed Databases, Distributed
  • From: Arthur Silva
• Help with PostgreSQL 9.4 to expand jsonb int array into table with row numbers
  • From: Neil Tiffin
• Re: Basic question regarding insert
  • From: Anil Menon
• Re: Performance of UPDATE SET = FROM vs UPDATE SET = (SELECT ...)
  • From: pbj
• Re: STABLE vs. IMMUTABLE w.r.t. indexes
  • From: Tom Lane
• Re: Performance of UPDATE SET = FROM vs UPDATE SET = (SELECT ...)
  • From: Igor Neyman
• Re: Testing on Power 8 systems
  • From: John R Pierce
• Re: Testing on Power 8 systems
  • From: Georges Racinet
• Re: Testing on Power 8 systems
  • From: Devrim Gündüz
• Re: Testing on Power 8 systems
  • From: John R Pierce
• Testing on Power 8 systems
  • From: Georges Racinet
• STABLE vs. IMMUTABLE w.r.t. indexes
  • From: Moshe Jacobson
• COPY TO returning empty result with parallel ALTER TABLE
  • From: Sven Wegener
• Performance of UPDATE SET = FROM vs UPDATE SET = (SELECT ...)
  • From: pbj
• Re: How to implent the CONVERT ( data_type [ ( length ) ] , expression ) function in PostgreSQL
  • From: Adrian Klaver
• Re: How to implent the CONVERT ( data_type [ ( length ) ] , expression ) function in PostgreSQL
  • From: Emanuel Calvo
• How to implent the CONVERT ( data_type [ ( length ) ] , expression ) function in PostgreSQL
  • From: rohtodeveloper
• Re: PL/Python prepare example's use of setdefault
  • From: Jonathan Rogers
• Re: Converting char to varchar automatically
  • From: Andrus
• Re: PL/Python prepare example's use of setdefault
  • From: Peter Eisentraut
• Re: PL/Python prepare example's use of setdefault
  • From: Peter Eisentraut
• Re: Retrieving Data from table based on Date and Time.
  • From: VENKTESH GUTTEDAR
• Re: Retrieving Data from table based on Date and Time.
  • From: Stephen Cook
• Retrieving Data from table based on Date and Time.
  • From: VENKTESH GUTTEDAR
• Re: LOADing functions
  • From: Adrian Klaver
• Re: LOADing functions
  • From: Tom Lane
• LOADing functions
  • From: Andrew Becker
• Re: Query planning
  • From: Emanuel Calvo
• Re: Basic question regarding insert
  • From: John R Pierce
• Re: Basic question regarding insert
  • From: Adrian Klaver
• Basic question regarding insert
  • From: Anil Menon
• Re: PostgreSQL on tablet grade SSD ?
  • From: David Boreham
• Re: PostgreSQL on tablet grade SSD ?
  • From: Merlin Moncure
• Re: Planet Postgres
  • From: Torsten Förtsch
• Re: Planet Postgres
  • From: Magnus Hagander
• Query planning
  • From: Jayadevan M
• Re: Estimating WAL usage during pg_basebackup
  • From: Soni M
• Re: DBlink, postgres to DB2
  • From: Craig Ringer
• Re: DBlink, postgres to DB2
  • From: Devrim Gündüz
• Re: Unexpected planner behavior with *_pattern_ops index matching
  • From: Tom Lane
• Re: Unexpected planner behavior with *_pattern_ops index matching
  • From: Fabio Ugo Venchiarutti
• Re: Planet Postgres
  • From: Stephen Frost
• Re: Planet Postgres
  • From: Adrian Klaver
• Planet Postgres
  • From: Torsten Förtsch
• Estimating WAL usage during pg_basebackup
  • From: Mike Blackwell
• Re: syntax error while using pg_dump in Postgres 8.4
  • From: David G Johnston
• Re: Appending new data to existing field of Json data type
  • From: VENKTESH GUTTEDAR
• Re: syntax error while using pg_dump in Postgres 8.4
  • From: David G Johnston
• Re: Appending new data to existing field of Json data type
  • From: Adrian Klaver
• Re: Appending new data to existing field of Json data type
  • From: Adrian Klaver
• Re: Unexpected planner behavior with *_pattern_ops index matching
  • From: Tom Lane
• PostgreSQL on tablet grade SSD ?
  • From: Karsten Hilbert
• Re: DBlink, postgres to DB2
  • From: Pavel Stehule
• Re: DBlink, postgres to DB2
  • From: Postgres India
• Re: Appending new data to existing field of Json data type
  • From: VENKTESH GUTTEDAR
• Unexpected planner behavior with *_pattern_ops index matching
  • From: Fabio Ugo Venchiarutti
• Re: Query optimization
  • From: Jorge Arevalo
• Re: Query optimization
  • From: David Johnston
• Re: Query optimization
  • From: Tom Lane
• Re: Query optimization
  • From: Jorge Arevalo
• Re: Query optimization
  • From: David Johnston
• Re: Query optimization
  • From: Tom Lane
• Re: Query optimization
  • From: David Johnston
• Re: Query optimization
  • From: Jorge Arevalo
• Re: Appending new data to existing field of Json data type
  • From: Adrian Klaver
• Re: undefined struct 'pg_conn' on Windows7
  • From: Brilliantov Kirill Vladimirovich
• Re: undefined struct 'pg_conn' on Windows7
  • From: Albe Laurenz
• undefined struct 'pg_conn' on Windows7
  • From: Brilliantov Kirill Vladimirovich
• Re: Appending new data to existing field of Json data type
  • From: VENKTESH GUTTEDAR
• Re: Appending new data to existing field of Json data type
  • From: Michael Paquier
• Re: How to find earlest possible start times for given duration excluding reservations
  • From: Andrus
• Need Guidance on Appending new data to existing field of Json data type
  • From: VENKTESH GUTTEDAR
• Appending new data to existing field of Json data type
  • From: VENKTESH GUTTEDAR
• Re: [BUGS] Need guidance on regression.diffs
  • From: Romu Hu
• Re: [BUGS] Need guidance on regression.diffs
  • From: Tom Lane
• Re: [BUGS] Need guidance on regression.diffs
  • From: Michael Paquier
• Re: Query optimization
  • From: David G Johnston
• Re: Query optimization
  • From: David G Johnston
• Re: Need guidance on regression.diffs
  • From: Romu Hu
• Query optimization
  • From: Jorge Arevalo
• Re: How to find earlest possible start times for given duration excluding reservations
  • From: Thom Brown
• Re: How to find earlest possible start times for given duration excluding reservations
  • From: Andrus
• Re: How to find earlest possible start times for given duration excluding reservations
  • From: Thom Brown
• Re: cannot drop user
  • From: Michael P. Soulier
• Re: How to find earlest possible start times for given duration excluding reservations
  • From: Thom Brown
• Re: Need guidance on regression.diffs
  • From: Adrian Klaver
• Need guidance on regression.diffs
  • From: Romu Hu
• Re: Log-shipping replication in one machine
  • From: Adrian Klaver
• Re: pg killed by oom-killer, "invalid contrecord length 2190 at A6C/331AAA90" on slaves
  • From: basti
• Re: "can not able to find scan Function For making NoDB"
  • From: Adrian Klaver
• Re: Log-shipping replication in one machine
  • From: nurul [via PostgreSQL]
• "can not able to find scan Function For making NoDB"
  • From: Gaurav Kumar
• Re: How to find earlest possible start times for given duration excluding reservations
  • From: Andrus
• Re: some queries on standby preventing replication updates
  • From: Torsten Förtsch
• Re: some queries on standby preventing replication updates
  • From: David G Johnston
• Re: some queries on standby preventing replication updates
  • From: Emanuel Calvo
• Re: some queries on standby preventing replication updates
  • From: Joe Van Dyk
• Re: pg killed by oom-killer, "invalid contrecord length 2190 at A6C/331AAA90" on slaves
  • From: Joe Van Dyk
• Re: cannot drop user
  • From: Michael P. Soulier
• Re: cannot drop user
  • From: Tom Lane
• Re: cannot drop user
  • From: Jerry Sievers
• cannot drop user
  • From: Michael P. Soulier
• Re: How to find earlest possible start times for given duration excluding reservations
  • From: Thom Brown
• How to find earlest possible start times for given duration excluding reservations
  • From: Andrus
• Re: Build libpq on Win7 failed with error "U1045: spawn failed"
  • From: Adrian Klaver
• Re: pg killed by oom-killer, "invalid contrecord length 2190 at A6C/331AAA90" on slaves
  • From: Andres Freund
• Re: Build libpq on Win7 failed with error "U1045: spawn failed"
  • From: Brilliantov Kirill Vladimirovich
• Re: Build libpq on Win7 failed with error "U1045: spawn failed"
  • From: Adrian Klaver
• Build libpq on Win7 failed with error "U1045: spawn failed"
  • From: Brilliantov Kirill Vladimirovich
• Re: Importing binary data
  • From: Chris Ruprecht
• Re: Importing binary data
  • From: Tom Lane
• Re: Importing binary data
  • From: Chris Ruprecht
• Re: pg killed by oom-killer, "invalid contrecord length 2190 at A6C/331AAA90" on slaves
  • From: Emanuel Calvo
• Re: Importing binary data
  • From: David G Johnston
• Importing binary data
  • From: Chris Ruprecht
• Re: pg killed by oom-killer, "invalid contrecord length 2190 at A6C/331AAA90" on slaves
  • From: basti
• Re: pg killed by oom-killer, "invalid contrecord length 2190 at A6C/331AAA90" on slaves
  • From: Joe Van Dyk
• Re: pg killed by oom-killer, "invalid contrecord length 2190 at A6C/331AAA90" on slaves
  • From: basti
• Re: some queries on standby preventing replication updates
  • From: Emanuel Calvo
• Re: Change recovery configuration without restarting standby_node.
  • From: Emanuel Calvo
• Change recovery configuration without restarting standby_node.
  • From: sudalai
• Re: Non-capturing expressions
  • From: Francisco Olarte
• pg killed by oom-killer, "invalid contrecord length 2190 at A6C/331AAA90" on slaves
  • From: Joe Van Dyk
• Re: Finding date intersections
  • From: Joe Van Dyk
• Re: Finding date intersections
  • From: hari . fuchs
• Re: dblink password required
  • From: Oliver Kohll - Mailing Lists
• Re: Non-capturing expressions
  • From: Thom Brown
• Re: Emulating flexible regex replace
  • From: Francisco Olarte
• Non-capturing expressions
  • From: Thom Brown
• Re: Osx stopping to install
  • From: Adrian Klaver
• Re: dblink password required
  • From: Adrian Klaver
• Re: Finding date intersections
  • From: Joe Van Dyk
• Re: Finding date intersections
  • From: David G Johnston
• dblink password required
  • From: Oliver Kohll - Mailing Lists
• Re: Emulating flexible regex replace
  • From: twoflower
• Re: Emulating flexible regex replace
  • From: Francisco Olarte
• Re: Finding date intersections
  • From: John McKown
• Osx stopping to install
  • From: TigerNassau
• Re: is there a warm standby sync trigger?
  • From: Michael Paquier
• Re: ARMv5
  • From: Michael Paquier
• Re: Log-shipping replication in one machine
  • From: Michael Paquier
• Re: Log-shipping replication in one machine
  • From: John R Pierce
• Log-shipping replication in one machine
  • From: nurul [via PostgreSQL]
• ARMv5
  • From: Александр Глухов
• Re: Emulating flexible regex replace
  • From: twoflower
• Re: Emulating flexible regex replace
  • From: blackbee045
• Finding date intersections
  • From: Joe Van Dyk
• is there a warm standby sync trigger?
  • From: John Smith
• Re[2]: [GENERAL] DBlink, postgres to DB2
  • From: Миша Тюрин
• some queries on standby preventing replication updates
  • From: Joe Van Dyk
• Re: Emulating flexible regex replace
  • From: David G Johnston
• Emulating flexible regex replace
  • From: Francisco Olarte
• Re: Emulating flexible regex replace
  • From: David G Johnston
• Re: Emulating flexible regex replace
  • From: Tom Lane
• Emulating flexible regex replace
  • From: twoflower
• Re: Inconsistency between PgAdmin III GUI and SQL window ?
  • From: Daniel Begin
• Re: DBlink, postgres to DB2
  • From: Postgres India
• Re: Index scan vs indexonly scan method
  • From: Jeff Janes
• Re: Function runtime increases after 5 calls in the same session.
  • From: Ilya Ashchepkov
• Re: Index scan vs indexonly scan method
  • From: Enrico Pirozzi
• Re: Index scan vs indexonly scan method
  • From: Adrian Klaver
• Index scan vs indexonly scan method
  • From: Enrico Pirozzi
• Re: To increase RAM or not
  • From: Igor Neyman
• Re: To increase RAM or not
  • From: Emanuel Calvo
• Re: Inconsistency between PgAdmin III GUI and SQL window ?
  • From: Adrian Klaver
• Re: DBlink, postgres to DB2
  • From: Merlin Moncure
• Re: DBlink, postgres to DB2
  • From: Pavel Stehule
• Re: DBlink, postgres to DB2
  • From: Rémi Cura
• Re: DBlink, postgres to DB2
  • From: Rémi Cura
• DBlink, postgres to DB2
  • From: Postgres India
• Re: Inconsistency between PgAdmin III GUI and SQL window ?
  • From: Daniel Begin
• To increase RAM or not
  • From: Nikhil Daddikar
• Re: Function runtime increases after 5 calls in the same session.
  • From: Tom Lane
• Re: Function runtime increases after 5 calls in the same session.
  • From: Ilya Ashchepkov
• Re: Yosemite (OSX 10.0) problems with Postgresql
  • From: John R Pierce
• Re: Yosemite (OSX 10.0) problems with Postgresql
  • From: Craig Ringer
• Re: Inconsistency between PgAdmin III GUI and SQL window ?
  • From: Adrian Klaver
• Re: Inconsistency between PgAdmin III GUI and SQL window ?
  • From: David G Johnston
• Inconsistency between PgAdmin III GUI and SQL window ?
  • From: Daniel Begin
• Re: Yosemite (OSX 10.0) problems with Postgresql
  • From: TigerNassau
• Re: Yosemite (OSX 10.0) problems with Postgresql
  • From: Michael Paquier
• Re: Function runtime increases after 5 calls in the same session.
  • From: Marti Raudsepp
• Re: Yosemite (OSX 10.0) problems with Postgresql
  • From: Craig Ringer
• Function runtime increases after 5 calls in the same session.
  • From: Ilya I. Ashchepkov
• Re: ALTER TYPE ... ADD VALUE issue
  • From: David G Johnston
• Re: ALTER TYPE ... ADD VALUE issue
  • From: Adrian Klaver
• Re: ALTER TYPE ... ADD VALUE issue
  • From: Adrian Klaver
• Re: ALTER TYPE ... ADD VALUE issue
  • From: Tom Lane
• Re: ALTER TYPE ... ADD VALUE issue
  • From: Victor Yegorov
• Re: ALTER TYPE ... ADD VALUE issue
  • From: Adrian Klaver
• ALTER TYPE ... ADD VALUE issue
  • From: Victor Yegorov
• Re: problem in to_char( ) ?
  • From: David G Johnston
• problem in to_char( ) ?
  • From: Day, David
• Re: Yosemite (OSX 10.0) problems with Postgresql
  • From: Tom Lane
• Re: Yosemite (OSX 10.0) problems with Postgresql
  • From: Wells Oliver
• Re: Yosemite (OSX 10.0) problems with Postgresql
  • From: Craig Ringer
• Re: Yosemite (OSX 10.0) problems with Postgresql
  • From: Israel Brewster
• Re: Yosemite (OSX 10.0) problems with Postgresql
  • From: Raghu Ram
• Re: Yosemite (OSX 10.0) problems with Postgresql
  • From: Jerry Levan
• Re: Yosemite (OSX 10.0) problems with Postgresql
  • From: Michael Paquier
• Yosemite (OSX 10.0) problems with Postgresql
  • From: Jerry Levan
• Re: 9.3 view / cross join / flat table solution
  • From: marin
• Re: Row number estimation...
  • From: marin
• 9.3 view / cross join / flat table solution
  • From: Wells Oliver
• Re: Row number estimation...
  • From: Tom Lane
• Re: Integrating C++ singletons into postgresql extensions???
  • From: Tom Lane
• Re: Integrating C++ singletons into postgresql extensions???
  • From: Stephen Woodbridge
• Re: Integrating C++ singletons into postgresql extensions???
  • From: Andres Freund
• Row number estimation...
  • From: marin
• Re: Integrating C++ singletons into postgresql extensions???
  • From: Dmitriy Igrishin
• Re: Hiding users and databases
  • From: Andreas Kretschmer
• Re: Hiding users and databases
  • From: Bruce Momjian
• Integrating C++ singletons into postgresql extensions???
  • From: Stephen Woodbridge
• Re: Will pg_repack improve this query performance?
  • From: aron123
• Hiding users and databases
  • From: Ross Dougherty
• Re: PgAgent binary distribution for Centos 6.5
  • From: Devrim Gündüz
• Re: FDW wrapper for clustered app management
  • From: Albe Laurenz
• Re: FDW wrapper for clustered app management
  • From: Jerome Wagner
• Re: FDW wrapper for clustered app management
  • From: Jerome Wagner
• Re: FDW wrapper for clustered app management
  • From: Albe Laurenz
• Re: FDW wrapper for clustered app management
  • From: John R Pierce
• FDW wrapper for clustered app management
  • From: Jerome Wagner
• Re: Weird library problem
  • From: Adrian Klaver
• Re: Weird library problem
  • From: Adrian Klaver
• Re: Will pg_repack improve this query performance?
  • From: Abelard Hoffman
• Re: Will pg_repack improve this query performance?
  • From: Josh Kupershmidt
• Re: COPY data into a table with a SERIAL column?
  • From: Adrian Klaver
• Re: Any postgres API available to get errorcode for PQerrorMessage
  • From: Adrian Klaver
• CopyManager(In/out) vs. delete/insert directly
  • From: Emi Lu
• Re: Tables used in query not listed in EXPLAIN
  • From: Tom Lane
• Tables used in query not listed in EXPLAIN
  • From: Alvaro Melo
• Re: Newb question - PostgreSQL ODBC Driver for Teiid
  • From: Adrian Klaver
• Re: COPY data into a table with a SERIAL column?
  • From: Steve Wampler
• Re: Misunderstanding deadlocks
  • From: Bill Moran
• Re: Misunderstanding deadlocks
  • From: Igor Neyman
• Re: COPY data into a table with a SERIAL column?
  • From: Rob Sargent
• Re: COPY data into a table with a SERIAL column?
  • From: David G Johnston
• Re: How to Install Extensions
  • From: Andreas Kretschmer
• Re: How to Install Extensions
  • From: Pavel Stehule
• Re: COPY data into a table with a SERIAL column?
  • From: Rob Sargent
• Re: COPY data into a table with a SERIAL column?
  • From: Rob Sargent
• Re: COPY data into a table with a SERIAL column?
  • From: David G Johnston
• Newb question - PostgreSQL ODBC Driver for Teiid
  • From: Conover, Paul W
• How to Install Extensions
  • From: Naveen Krishna
• Re: Any postgres API available to get errorcode for PQerrorMessage
  • From: Roopeshakumar Narayansa Shalgar (rshalgar)
• Re: COPY data into a table with a SERIAL column?
  • From: Steve Wampler
• Misunderstanding deadlocks
  • From: snacktime
• Re: COPY data into a table with a SERIAL column?
  • From: Rob Sargent
• COPY data into a table with a SERIAL column?
  • From: Steve Wampler
• Re: How to start several PostgreSQL clusters at boot time on a Debian OS
  • From: Léa Massiot
• Re: Weird library problem
  • From: Holger.Friedrich-Fa-Trivadis
• Re: Weird library problem
  • From: Adrian Klaver
• Weird library problem
  • From: Holger.Friedrich-Fa-Trivadis
• Re: library path problems?
  • From: Adrian Klaver
• Re: library path problems? (was: Completely unrelated)
  • From: John R Pierce
• Re: Any postgres API available to get errorcode for PQerrorMessage
  • From: Yogesh. Sharma
• Re: PL/Python prepare example's use of setdefault
  • From: Jonathan Rogers
• Re: PL/Python prepare example's use of setdefault
  • From: Tom Lane
• Re: PL/Python prepare example's use of setdefault
  • From: Adrian Klaver
• PL/Python prepare example's use of setdefault
  • From: Jonathan Rogers
• Re: Any postgres API available to get errorcode for PQerrorMessage
  • From: John R Pierce
• Re: Any postgres API available to get errorcode for PQerrorMessage
  • From: Roopeshakumar Narayansa Shalgar (rshalgar)
• Re: Any postgres API available to get errorcode for PQerrorMessage
  • From: Rob Sargent
• Re: Any postgres API available to get errorcode for PQerrorMessage
  • From: Tom Lane
• Any postgres API available to get errorcode for PQerrorMessage
  • From: Roopeshakumar Narayansa Shalgar (rshalgar)
• Re: How to start several PostgreSQL clusters at boot time on a Debian OS
  • From: Adrian Klaver
• Re: How to start several PostgreSQL clusters at boot time on a Debian OS
  • From: Léa Massiot
• Re: How to start several PostgreSQL clusters at boot time on a Debian OS
  • From: Guillaume Lelarge
• How to start several PostgreSQL clusters at boot time on a Debian OS
  • From: Léa Massiot
• Re: Will pg_repack improve this query performance?
  • From: Alban Hertroys
• Re: copying a large database to change encoding
  • From: Albe Laurenz
• Will pg_repack improve this query performance?
  • From: Abelard Hoffman
• Re: copying a large database to change encoding
  • From: Vick Khera
• Re: copying a large database to change encoding
  • From: Adrian Klaver
• Re: copying a large database to change encoding
  • From: Matthew Chambers
• Re: copying a large database to change encoding
  • From: Adrian Klaver
• copying a large database to change encoding
  • From: Matthew Chambers
• Re: Where should I post 3rd party product announcements?
  • From: Alvaro Herrera
• listen from slave database
  • From: ChoonSoo Park
• Mailing list pgbr-geral
  • From: Mauro Sérgio
• Re: Optimal checkpoint_setting
  • From: pinker
• Re: Where should I post 3rd party product announcements?
  • From: Jonathan Neve
• Re: Where should I post 3rd party product announcements?
  • From: Magnus Hagander
• Re: Where should I post 3rd party product announcements?
  • From: Jonathan Neve
• Re: Where should I post 3rd party product announcements?
  • From: Magnus Hagander
• Re: Where should I post 3rd party product announcements?
  • From: Atri Sharma
• Re: Where should I post 3rd party product announcements?
  • From: Jonathan Neve
• Re: Where should I post 3rd party product announcements?
  • From: Amit Langote
• Where should I post 3rd party product announcements?
  • From: Jonathan Neve
• Re: FK check implementation
  • From: Nick Barnes
• Re: 9.3 migration issue
  • From: Stephen Davies
• Re: 9.3 migration issue
  • From: Adrian Klaver
• Re: 9.3 migration issue
  • From: Stephen Davies
• Re: Processor usage/tuning question
  • From: Israel Brewster
• Re: 9.3 migration issue
  • From: Adrian Klaver
• Re: 9.3 migration issue
  • From: Stephen Davies
• Re: 9.3 migration issue
  • From: Stephen Davies
• Re: 9.3 migration issue
  • From: Jeff Janes
• Re: 9.3 migration issue
  • From: Vick Khera
• Re: pg advisory locks
  • From: Alban Hertroys
• 9.3 migration issue
  • From: Stephen Davies
• Re: pg advisory locks
  • From: Arun Gokule
• pg advisory locks
  • From: Arun Gokule
• Re: Processor usage/tuning question
  • From: Jeff Janes
• Re: psql connection issue
  • From: Stephen Davies
• Re: Processor usage/tuning question
  • From: Jim Nasby
• Re: table versioning approach (not auditing)
  • From: Jim Nasby
• Re: How to synchronize tables in remote (production) and local databases in case if the structure of local database's table has been modified
  • From: Jim Nasby
• Re: psql connection issue
  • From: Jim Nasby
• Re: Converting char to varchar automatically
  • From: Jim Nasby
• Re: psql generate insert command based on select
  • From: vibhor.kumar@xxxxxxxxxxxxxxxx
• Re: FK check implementation
  • From: Adrian Klaver
• Re: psql generate insert command based on select
  • From: "Leonardo M. Ramé"
• Re: psql generate insert command based on select
  • From: Adrian Klaver
• Re: psql generate insert command based on select
  • From: vibhor.kumar@xxxxxxxxxxxxxxxx
• Re: Understanding and implementing a GiST Index
  • From: Connor Wolf
• Re: psql generate insert command based on select
  • From: "Leonardo M. Ramé"
• Re: FK check implementation
  • From: Nick Barnes
• Re: psql generate insert command based on select
  • From: Adrian Klaver
• psql generate insert command based on select
  • From: "Leonardo M. Ramé"
• Re: org.postgresql.copy.CopyManager which JDBC version ?
  • From: Adrian Klaver
• Re: org.postgresql.copy.CopyManager which JDBC version ?
  • From: Tim Clarke
• Re: org.postgresql.copy.CopyManager which JDBC version ?
  • From: Tim Clarke
• org.postgresql.copy.CopyManager which JDBC version ?
  • From: Emi Lu
• Re: FK check implementation
  • From: Tom Lane
• Re: PostgreSQL server won't start, corrupt?
  • From: Merlin Moncure
• FK check implementation
  • From: Nick Barnes
• Re: PostgreSQL server won't start, corrupt?
  • From: Adrian Klaver
• Re: PostgreSQL server won't start, corrupt?
  • From: John R Pierce
• Re: PostgreSQL server won't start, corrupt?
  • From: Rob Flemming
• Re: PostgreSQL server won't start, corrupt?
  • From: Adrian Klaver
• Re: PostgreSQL server won't start, corrupt?
  • From: Rob Flemming
• Re: PostgreSQL server won't start, corrupt?
  • From: Adrian Klaver
• Re: PostgreSQL server won't start, corrupt?
  • From: Rob Flemming
• Re: PostgreSQL server won't start, corrupt?
  • From: John R Pierce
• Re: PostgreSQL server won't start, corrupt?
  • From: Raymond O'Donnell
• Re: Optimal checkpoint_setting
  • From: Kevin Grittner
• Re: PostgreSQL server won't start, corrupt?
  • From: Ray Stell
• Re: PostgreSQL server won't start, corrupt?
  • From: John R Pierce
• Re: PostgreSQL server won't start, corrupt?
  • From: John R Pierce
• Re: PostgreSQL server won't start, corrupt?
  • From: Raymond O'Donnell
• Re: Optimal checkpoint_setting
  • From: John R Pierce
• PostgreSQL server won't start, corrupt?
  • From: Rob Flemming
• Re: Optimal checkpoint_setting
  • From: Dennis
• Re: Optimal checkpoint_setting
  • From: Jeff Janes
• Re: Understanding and implementing a GiST Index
  • From: Sergey Konoplev
• Understanding and implementing a GiST Index
  • From: Connor Wolf
• Re: Converting char to varchar automatically
  • From: hari . fuchs
• Optimal checkpoint_setting
  • From: pinker
• Re: Importing large object (with lo_import) to table in separate tablespaces takes up lots of space in $PGDATA
  • From: Andreas Joseph Krogh
• Re: Converting char to varchar automatically
  • From: Andrus
• Re: Importing large object (with lo_import) to table in separate tablespaces takes up lots of space in $PGDATA
  • From: Guillaume Lelarge
• Re: psql connection issue
  • From: Stephen Davies
• Importing large object (with lo_import) to table in separate tablespaces takes up lots of space in $PGDATA
  • From: Andreas Joseph Krogh
• Re: Converting char to varchar automatically
  • From: Melvin Davidson
• Re: Converting char to varchar automatically
  • From: Andrus
• Re: How to synchronize tables in remote (production) and local databases in case if the structure of local database's table has been modified
  • From: Sergey Konoplev
• Re: Converting char to varchar automatically
  • From: Melvin Davidson
• Re: Sync production DB with development?
  • From: Jeff Ross
• Re: Sync production DB with development?
  • From: Emanuel Calvo
• Re: Sync production DB with development?
  • From: Greg Sabino Mullane
• Re: Sync production DB with development?
  • From: Israel Brewster
• Re: Processor usage/tuning question
  • From: Israel Brewster
• Re: Converting char to varchar automatically
  • From: Andrus
• Re: Processor usage/tuning question
  • From: Jeff Janes
• Re: Sync production DB with development?
  • From: Emanuel Calvo
• Sync production DB with development?
  • From: Israel Brewster
• Re: Convert raw fields into Datum
  • From: Tom Lane
• Re: psql connection issue
  • From: Adrian Klaver
• Convert raw fields into Datum
  • From: sri harsha
• Re: Converting char to varchar automatically
  • From: Andrus
• How to synchronize tables in remote (production) and local databases in case if the structure of local database's table has been modified
  • From: Vitaly Isaev
• Re: psql connection issue
  • From: Stephen Davies
• Re: psql connection issue
  • From: Ian Barwick
• Re: psql connection issue
  • From: Tom Lane
• psql connection issue
  • From: Stephen Davies
• Re: table versioning approach (not auditing)
  • From: Gavin Flower
• Re: Processor usage/tuning question
  • From: israel
• Re: Converting char to varchar automatically
  • From: Jim Nasby
• Re: table versioning approach (not auditing)
  • From: Jim Nasby
• Re: index behavior question - multicolumn not consulted ?
  • From: John R Pierce
• index behavior question - multicolumn not consulted ?
  • From: Jonathan Vanasco
• Re: Converting char to varchar automatically
  • From: Sergey Konoplev
• Re: Converting char to varchar automatically
  • From: Tom Lane
• Re: Converting char to varchar automatically
  • From: Sergey Konoplev
• Re: Converting char to varchar automatically
  • From: Tom Lane
• Re: faster way to calculate top "tags" for a "resource" based on a column
  • From: Jonathan Vanasco
• Re: Converting char to varchar automatically
  • From: Sergey Konoplev
• Re: faster way to calculate top "tags" for a "resource" based on a column
  • From: Marc Mamin
• Re: Really strange foreign key constraint problem blocking delete
  • From: Tom Lane
• Re: Processor usage/tuning question
  • From: Emanuel Calvo
• Re: Really strange foreign key constraint problem blocking delete
  • From: Adrian Klaver
• Re: Really strange foreign key constraint problem blocking delete
  • From: Adrian Klaver
• Re: How to get good performance for very large lists/sets?
  • From: Alban Hertroys
• Re: Really strange foreign key constraint problem blocking delete
  • From: Tim Mickelson
• Re: Converting char to varchar automatically
  • From: Tom Lane
• Re: Converting char to varchar automatically
  • From: Tom Lane
• Re: table versioning approach (not auditing)
  • From: Gavin Flower
• Re: faster way to calculate top "tags" for a "resource" based on a column
  • From: Jonathan Vanasco
• Re: Converting char to varchar automatically
  • From: Melvin Davidson
• Re: How to get good performance for very large lists/sets?
  • From: Jim Nasby
• Re: Converting char to varchar automatically
  • From: Jim Nasby
• Re: Really strange foreign key constraint problem blocking delete
  • From: Jim Nasby
• Re: <idle> question
  • From: Jim Nasby
• Re: Processor usage/tuning question
  • From: Jim Nasby
• Re: faster way to calculate top "tags" for a "resource" based on a column
  • From: Jim Nasby
• Re: table versioning approach (not auditing)
  • From: Jim Nasby
• Re: How to get good performance for very large lists/sets?
  • From: Andy Colson
• Re: How to get good performance for very large lists/sets?
  • From: Jeff Janes
• Re: How to get good performance for very large lists/sets?
  • From: Andy Colson
• Re: How to get good performance for very large lists/sets?
  • From: Richard Frith-Macdonald
• Re: How to get good performance for very large lists/sets?
  • From: Igor Neyman
• Re: How to get good performance for very large lists/sets?
  • From: François Beausoleil
• Re: Converting char to varchar automatically
  • From: hari . fuchs
• Re: How to get good performance for very large lists/sets?
  • From: Andy Colson
• Re: Converting char to varchar automatically
  • From: Andrus
• Re: How to get good performance for very large lists/sets?
  • From: Igor Neyman
• Re: How does PostgerSQL planner decide driving table
  • From: Emanuel Calvo
• How to get good performance for very large lists/sets?
  • From: Richard Frith-Macdonald
• Re: Converting char to varchar automatically
  • From: Melvin Davidson
• Re: Really strange foreign key constraint problem blocking delete
  • From: Tim Mickelson
• Re: <idle> question
  • From: Andy Colson
• Re: How to find greatest record before known values fast
  • From: Merlin Moncure
• <idle> question
  • From: Emi Lu
• Re: Converting char to varchar automatically
  • From: Andy Colson
• Converting char to varchar automatically
  • From: Andrus
• How does PostgerSQL planner decide driving table
  • From: Shingo horiuchi
• Re: Really strange foreign key constraint problem blocking delete
  • From: Andy Colson
• Re: Really strange foreign key constraint problem blocking delete
  • From: Adrian Klaver
• Re: Really strange foreign key constraint problem blocking delete
  • From: Andy Colson
• Re: Really strange foreign key constraint problem blocking delete
  • From: Tim Mickelson
• Re: Really strange foreign key constraint problem blocking delete
  • From: Adrian Klaver
• Re: Really strange foreign key constraint problem blocking delete
  • From: Tim Mickelson
• Re: Really strange foreign key constraint problem blocking delete
  • From: Tim Mickelson
• Re: How to find greatest record before known values fast
  • From: Andrus
• Re: How to find greatest record before known values fast
  • From: Andrus
• Re: How to callproc a PL/pgSQL function a cursor OUT parameter and two OUT parameters
  • From: Adrian Klaver
• Re: How to callproc a PL/pgSQL function a cursor OUT parameter and two OUT parameters
  • From: Adrian Klaver
• How to callproc a PL/pgSQL function a cursor OUT parameter and two OUT parameters
  • From: Néstor Boscán
• Re: Really strange foreign key constraint problem blocking delete
  • From: Andy Colson
• Re: Really strange foreign key constraint problem blocking delete
  • From: Adrian Klaver
• Re: Really strange foreign key constraint problem blocking delete
  • From: Tim Mickelson
• Re: Processor usage/tuning question
  • From: Andy Colson
• Re: How to find greatest record before known values fast
  • From: Adrian Klaver
• Re: How to find greatest record before known values fast
  • From: Tom Lane
• Re: How to find greatest record before known values fast
  • From: Adrian Klaver
• Re: Processor usage/tuning question
  • From: Alan Hodgson
• Processor usage/tuning question
  • From: Israel Brewster
• Re: How to find greatest record before known values fast
  • From: Merlin Moncure
• Re: How to find greatest record before known values fast
  • From: Andrus
• Re: Really strange foreign key constraint problem blocking delete
  • From: Vick Khera
• faster way to calculate top "tags" for a "resource" based on a column
  • From: Jonathan Vanasco
• Really strange foreign key constraint problem blocking delete
  • From: Tim Mickelson
• Re: installing on mac air development machine
  • From: john gale
• Re: How to find greatest record before known values fast
  • From: Merlin Moncure
• Re: Getting my Database name in a C Extension
  • From: Cedric Berger
• Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
  • From: Andrej Vanek
• Re: Getting my Database name in a C Extension
  • From: Michael Paquier
• Re: Getting my Database name in a C Extension
  • From: Albe Laurenz
• Re: PostgreSQL Inheritance and column mapping
  • From: Achilleas Mantzios
• Re: Getting my Database name in a C Extension
  • From: Cedric Berger
• Re: How to find greatest record before known values fast
  • From: Andrus
• Re: Creating a PL/pgSQL function that returns multiple out parameters and refcursor
  • From: Michael Paquier
• Re: installing on mac air development machine
  • From: Steve Atkins
• Re: How to find greatest record before known values fast
  • From: Tom Lane
• Re: installing on mac air development machine
  • From: John R Pierce
• Re: How to find greatest record before known values fast
  • From: David G Johnston
• Re: PostgreSQL Inheritance and column mapping
  • From: Jim Nasby
• Re: How to find greatest record before known values fast
  • From: Jim Nasby
• Re: Creating index on concatenated char columns fails is Postgres 9 (regression)
  • From: Adrian Klaver
• Re: installing on mac air development machine
  • From: Adrian Klaver
• Re: installing on mac air development machine
  • From: Jonathan Vanasco
• Re: installing on mac air development machine
  • From: john gale
• Re: installing on mac air development machine
  • From: Ian Barwick
• Re: Getting my Database name in a C Extension
  • From: John R Pierce
• installing on mac air development machine
  • From: john.tiger
• Getting my Database name in a C Extension
  • From: Cedric Berger
• How to find greatest record before known values fast
  • From: Andrus
• Creating index on concatenated char columns fails is Postgres 9 (regression)
  • From: Andrus
• Benching Queries
  • From: Jonathan Vanasco
• Re: Postgres tcp_keepalive_xxxx parameters.
  • From: José Luis Rando Calvo
• Creating a PL/pgSQL function that returns multiple out parameters and refcursor
  • From: Néstor Boscán
• Re: Getting my Database name in a C Extension
  • From: Tom Lane
• Getting my Database name in a C Extension
  • From: Cedric Berger
• Re: table versioning approach (not auditing)
  • From: Adam Brusselback
• Re: table versioning approach (not auditing)
  • From: Adam Brusselback
• Re: PostgreSQL Inheritance and column mapping
  • From: Tom Lane
• Re: PostgreSQL Inheritance and column mapping
  • From: John R Pierce
• PostgreSQL Inheritance and column mapping
  • From: Achilleas Mantzios
• Re: Extract especific text from a sql statement
  • From: David G Johnston
• Re: Extract especific text from a sql statement
  • From: Melvin Davidson
• Re: Is there a way to get both the plan and the results?
  • From: David G Johnston
• Is there a way to get both the plan and the results?
  • From: François Beausoleil
• Re: improving speed of query that uses a multi-column "filter" ?
  • From: Jonathan Vanasco
• Re: Extract especific text from a sql statement
  • From: David G Johnston
• Re: table versioning approach (not auditing)
  • From: Adam Brusselback
• Re: Postgres tcp_keepalive_xxxx parameters.
  • From: Tom Lane
• Re: Best practices for Large import in empty database?
  • From: Daniel Begin
• Postgres tcp_keepalive_xxxx parameters.
  • From: jlrando
• Re: Best practices for Large import in empty database?
  • From: Andy Colson
• Re: Best practices for Large import in empty database?
  • From: Tom Lane
• Best practices for Large import in empty database?
  • From: Daniel Begin
• Extract especific text from a sql statement
  • From: Emanuel Araújo
• Re: table versioning approach (not auditing)
  • From: Felix Kunde
• Re: improving speed of query that uses a multi-column "filter" ?
  • From: Misa Simic
• Re: improving speed of query that uses a multi-column "filter" ?
  • From: Jonathan Vanasco
• Re: improving speed of query that uses a multi-column "filter" ?
  • From: John R Pierce
• improving speed of query that uses a multi-column "filter" ?
  • From: Jonathan Vanasco
• ability to return number of rows inserted into child partition tables request
  • From: Roger Pack
• Re: [SQL] pg_multixact issues
  • From: Dev Kumkar
• Re: table versioning approach (not auditing)
  • From: Adam Brusselback
• Re: synchronize DTAP
  • From: Brent Wood
• Re: [SQL] pg_multixact issues
  • From: Alvaro Herrera
• Re: [SQL] pg_multixact issues
  • From: Dev Kumkar
• Re: BDR Global Sequences
  • From: pbj
• Re: PANIC: could not create file "pg_xlog/xlogtemp.7884": No space left on device
  • From: Eric Veldhuyzen
• Re: table versioning approach (not auditing)
  • From: Felix Kunde
• Re: BDR Global Sequences
  • From: Andres Freund
• synchronize DTAP
  • From: Willy-Bas Loos
• Re: Postgres as key/value store
  • From: Jonathan Vanasco
• Re: PG 9.3 Switch streaming to wal shipping
  • From: Andy Colson
• Re: PG 9.3 Switch streaming to wal shipping
  • From: Adrian Klaver
• Re: table versioning approach (not auditing)
  • From: Jonathan Vanasco
• Re: table versioning approach (not auditing)
  • From: Abelard Hoffman
• Re: PG 9.3 Switch streaming to wal shipping
  • From: Andy Colson
• BDR Global Sequences
  • From: pbj
• PG 9.3 Switch streaming to wal shipping
  • From: Andy Colson
• Re: table versioning approach (not auditing)
  • From: Nick Guenther
• Re: table versioning approach (not auditing)
  • From: Jonathan Vanasco
• Re: table versioning approach (not auditing)
  • From: Felix Kunde
• Re: table versioning approach (not auditing)
  • From: Gavin Flower
• table versioning approach (not auditing)
  • From: Abelard Hoffman
• Re: [SQL] how to see "where" SQL is better than PLPGSQL
  • From: Pavel Stehule
• Re: [SQL] how to see "where" SQL is better than PLPGSQL
  • From: Gerardo Herzig
• Re: PANIC: could not create file "pg_xlog/xlogtemp.7884": No space left on device
  • From: Tom Lane
• Re: [SQL] how to see "where" SQL is better than PLPGSQL
  • From: Pavel Stehule
• how to see "where" SQL is better than PLPGSQL
  • From: Gerardo Herzig
• Re: PANIC: could not create file "pg_xlog/xlogtemp.7884": No space left on device
  • From: Adrian Klaver
• Re: call pl/pgsql function from main pl/pgsql function
  • From: Jov
• Re: PANIC: could not create file "pg_xlog/xlogtemp.7884": No space left on device
  • From: Roopeshakumar Narayansa Shalgar (rshalgar)
• Re: call pl/pgsql function from main pl/pgsql function
  • From: David G Johnston
• call pl/pgsql function from main pl/pgsql function
  • From: Mehdi Ravanbakhsh
• Re: Postgres as key/value store
  • From: Thomas Kellerer
• Re: Postgres as key/value store
  • From: Gavin Flower
• Postgres as key/value store
  • From: snacktime
• Re: password in recovery.conf [SOLVED]
  • From: Nelson Green
• Re: password in recovery.conf [SOLVED]
  • From: Nelson Green
• Re: Window function with valued based range frames?
  • From: Tom Lane
• Window function with valued based range frames?
  • From: David G Johnston
• Re: password in recovery.conf [SOLVED]
  • From: Gavin Flower
• Re: password in recovery.conf [SOLVED]
  • From: John R Pierce
• Re: password in recovery.conf [SOLVED]
  • From: Adrian Klaver
• Re: password in recovery.conf [SOLVED]
  • From: John R Pierce
• Re: password in recovery.conf [SOLVED]
  • From: Nelson Green
• Re: password in recovery.conf
  • From: Adrian Klaver
• Re: advice sought - general approaches to optimizing queries around "event streams"
  • From: Brent Wood
• Re: password in recovery.conf
  • From: DrakoRod
• Re: advice sought - general approaches to optimizing queries around "event streams"
  • From: Gavin Flower
• advice sought - general approaches to optimizing queries around "event streams"
  • From: Jonathan Vanasco
• Re: password in recovery.conf
  • From: Bosco Rama
• password in recovery.conf
  • From: Nelson Green
• Re: PANIC: could not create file "pg_xlog/xlogtemp.7884": No space left on device
  • From: David G Johnston
• Re: PANIC: could not create file "pg_xlog/xlogtemp.7884": No space left on device
  • From: Raymond O'Donnell
• Re: PANIC: could not create file "pg_xlog/xlogtemp.7884": No space left on device
  • From: Raymond O'Donnell
• PANIC: could not create file "pg_xlog/xlogtemp.7884": No space left on device
  • From: Roopeshakumar Narayansa Shalgar (rshalgar)
• Re: Procedure after failover
  • From: Paul Jungwirth
• Procedure after failover
  • From: Paul Jungwirth
• Postgres Standby
  • From: Derek Giri
• Re: [SQL] pg_multixact issues
  • From: Dev Kumkar
• Re: wide row insert via Postgres jdbc driver
  • From: Sameer Kumar
• Re: Off Topic: Anybody reading this via news.gmane.org?
  • From: Ian Pilcher
• Off Topic: Anybody reading this via news.gmane.org?
  • From: George Neuner
• Re: Synchronous replication + pgPool: not all transactions immediately visible on standby
  • From: Tatsuo Ishii
• Re: Re: Synchronous replication + pgPool: not all transactions immediately visible on standby
  • From: Tatsuo Ishii
• Re: Synchronous replication + pgPool: not all transactions immediately visible on standby
  • From: Kevin Grittner
• Re: Synchronous replication + pgPool: not all transactions immediately visible on standby
  • From: Thomas Kellerer
• Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
  • From: Alvaro Herrera
• Re: Installing Postgresql on Linux Friendlyarm
  • From: Adrian Klaver
• Re: How to clone CURRENT_DATE to SYSDATE ?
  • From: Adrian Klaver
• Re: Synchronous replication + pgPool: not all transactions immediately visible on standby
  • From: Michael Paquier
• Re: How to clone CURRENT_DATE to SYSDATE ?
  • From: Pavel Stehule
• Re: How to clone CURRENT_DATE to SYSDATE ?
  • From: Emanuel Araújo
• Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
  • From: Andrej Vanek
• Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
  • From: Andrej Vanek
• Re: Installing Postgresql on Linux Friendlyarm
  • From: Xiang Gan
• Re: spgist index not getting used
  • From: Paul Ramsey
• Re: spgist index not getting used
  • From: Tom Lane
• Re: spgist index not getting used
  • From: Paul Ramsey
• Re: Synchronous replication + pgPool: not all transactions immediately visible on standby
  • From: Tatsuo Ishii
• Re: spgist index not getting used
  • From: Peter Geoghegan
• spgist index not getting used
  • From: Paul Ramsey
• Re: JSONB spaces in text presentation
  • From: Seref Arikan
• Re: Transaction completion timing
  • From: Steve Dodd
• Re: How to clone CURRENT_DATE to SYSDATE ?
  • From: Adrian Klaver
• Re: JSONB spaces in text presentation
  • From: John R Pierce
• Re: JSONB spaces in text presentation
  • From: Oleg Bartunov
• Re: Custom type literal conversion
  • From: Chris Bandy
• Re: Why can't I select un-grouped columns when grouping by a (non-primary) unique key?
  • From: Tom Lane
• Re: Why can't I select un-grouped columns when grouping by a (non-primary) unique key?
  • From: Daniel Lenski
• Re: Why can't I select un-grouped columns when grouping by a (non-primary) unique key?
  • From: Daniel Lenski
• Re: Transaction completion timing
  • From: Tom Lane
• Transaction completion timing
  • From: Steve Dodd
• Re: Why can't I select un-grouped columns when grouping by a (non-primary) unique key?
  • From: Geoff Montee
• Re: Why can't I select un-grouped columns when grouping by a (non-primary) unique key?
  • From: Alberto Cabello Sánchez
• Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
  • From: Bill Moran
• Re: JSONB spaces in text presentation
  • From: Ilya I. Ashchepkov
• Re: Question about row_number() ordering semantics
  • From: Tom Lane
• Re: JSONB spaces in text presentation
  • From: Ilya I. Ashchepkov
• Why can't I select un-grouped columns when grouping by a (non-primary) unique key?
  • From: Daniel Lenski
• Re: [ADMIN] readonly user
  • From: Geoff Winkless
• Question about row_number() ordering semantics
  • From: Fred Jonsson
• [ADMIN] readonly user
  • From: Stefan Carl
• How to clone CURRENT_DATE to SYSDATE ?
  • From: Emanuel Araújo
• Re: JSONB spaces in text presentation
  • From: Adrian Klaver
• Re: JSONB spaces in text presentation
  • From: Seref Arikan
• Re: JSONB spaces in text presentation
  • From: Adrian Klaver
• Re: JSONB spaces in text presentation
  • From: Merlin Moncure
• Re: Custom type literal conversion
  • From: hubert depesz lubaczewski
• Custom type literal conversion
  • From: Chris Bandy
• Re: pg_dump: [archiver] -C and -c are incompatible options
  • From: Tom Lane
• Synchronous replication + pgPool: not all transactions immediately visible on standby
  • From: Thomas Kellerer
• Re: JSONB spaces in text presentation
  • From: Ilya I. Ashchepkov
• Re: JSONB spaces in text presentation
  • From: John R Pierce
• JSONB spaces in text presentation
  • From: Ilya I. Ashchepkov
• JSONB spaces in text presentation
  • From: Ilya I. Ashchepkov
• Re: PROBLEM Service Alert: hostname/check_postgres_old_transaction is CRITICAL **
  • From: Adarsh Sharma
• JSONB spaces in text presentation
  • From: Ilya I. Ashchepkov
• Re: pg_dump: [archiver] -C and -c are incompatible options
  • From: David G Johnston
• Re: pg_dump: [archiver] -C and -c are incompatible options
  • From: Adrian Klaver
• Re: pg_dump: [archiver] -C and -c are incompatible options
  • From: Tom Lane
• pg_dump: [archiver] -C and -c are incompatible options
  • From: Carlos Carcamo
• Fwd: Re: Where art thou, plpython2.dll? (EDB installer)
  • From: Nick Guenther
• Re: which Update quicker
  • From: Steve Crawford
• Re: which Update quicker
  • From: Daniele Varrazzo
• which Update quicker
  • From: Emi Lu
• Re: Where art thou, plpython2.dll? (EDB installer)
  • From: Daniel Lenski
• Re: Where art thou, plpython2.dll? (EDB installer)
  • From: Adrian Klaver
• Re: Where art thou, plpython2.dll? (EDB installer)
  • From: Alan Hodgson
• Re: Where art thou, plpython2.dll? (EDB installer)
  • From: Nick Guenther
• deadlock of lock-waits (on transaction and on tuple) using same update statement
  • From: Andrej Vanek
• Re: fmgr_oldstyle in extensions
  • From: Paul Ramsey
• Re: fmgr_oldstyle in extensions
  • From: Andres Freund
• fmgr_oldstyle in extensions
  • From: Paul Ramsey
• Re: Will there be a JSON operator like ->> but returning numeric?
  • From: Tom Lane
• Re: Unexpected syntax error when using JSON -> in 9.3.5
  • From: Tom Lane
• Re: Unexpected syntax error when using JSON -> in 9.3.5
  • From: David G Johnston
• Re: Where art thou, plpython2.dll? (EDB installer)
  • From: Daniel Lenski
• Will there be a JSON operator like ->> but returning numeric?
  • From: Seamus Abshere
• Unexpected syntax error when using JSON -> in 9.3.5
  • From: Seamus Abshere
• Re: Question about Vacuum and Replication failures in 9.3.5
  • From: Adrian Klaver
• Re: Installing Postgresql on Linux Friendlyarm
  • From: Vick Khera
• Re: csv import error
  • From: Eugenio Trumpy
• Re: Employee modeling question
  • From: Nelson Green
• Re: wide row insert via Postgres jdbc driver
  • From: Bill Moran
• Re: wide row insert via Postgres jdbc driver
  • From: Thomas Kellerer
• Re: csv import error
  • From: FarjadFarid(ChkNet)
• Re: csv import error
  • From: Eugenio Trumpy
• Re: Where art thou, plpython2.dll? (EDB installer)
  • From: Seref Arikan
• Re: wide row insert via Postgres jdbc driver
  • From: Bill Moran
• Re: csv import error
  • From: FarjadFarid(ChkNet)
• Fw: strange problem with not existing roles
  • From: ludwig@xxxxxxxxxxxxx
• Re: csv import error
  • From: Rémi Cura
• Re: csv import error
  • From: FarjadFarid(ChkNet)
• csv import error
  • From: Eugenio Trumpy
• Where art thou, plpython2.dll? (EDB installer)
  • From: Craig Ringer
• Re: ALTER TEXT field to VARCHAR(1024)
  • From: Jeff Janes
• Re: Installing Postgresql on Linux Friendlyarm
  • From: Abelard Hoffman
• wide row insert via Postgres jdbc driver
  • From: Sameer Kumar
• Re: Question about Vacuum and Replication failures in 9.3.5
  • From: Joel Avni
• Re: Question about Vacuum and Replication failures in 9.3.5
  • From: Joel Avni
• Re: Installing Postgresql on Linux Friendlyarm
  • From: Tom Lane
• Re: Installing Postgresql on Linux Friendlyarm
  • From: Xiang Gan
• Re: Higher chance of deadlock due to ANALYZE VERBOSE / SHARE UPDATE EXCLUSIVE?
  • From: Tom Lane
• Higher chance of deadlock due to ANALYZE VERBOSE / SHARE UPDATE EXCLUSIVE?
  • From: Dean Toader
• Re: Question about Vacuum and Replication failures in 9.3.5
  • From: Adrian Klaver
• Question about Vacuum and Replication failures in 9.3.5
  • From: Joel Avni
• Re: large table
  • From: Luke Coldiron
• Re: large table
  • From: Bill Moran
• Re: large table
  • From: Eduardo Morras
• Re: large table
  • From: John R Pierce
• Re: large table
  • From: Luke Coldiron
• Re: large table
  • From: Luke Coldiron
• Re: large table
  • From: Bill Moran
• Re: large table
  • From: Alan Hodgson
• large table
  • From: Luke Coldiron
• Re: ALTER TEXT field to VARCHAR(1024)
  • From: Tom Lane
• Re: ALTER TEXT field to VARCHAR(1024)
  • From: David G Johnston
• Re: Postgre SQL SHA-256 Compliance
  • From: Karsten Hilbert
• Re: ALTER TEXT field to VARCHAR(1024)
  • From: Merlin Moncure
• Re: ALTER TEXT field to VARCHAR(1024)
  • From: John McKown
• Re: ALTER TEXT field to VARCHAR(1024)
  • From: Tim Clarke
• Re: ALTER TEXT field to VARCHAR(1024)
  • From: Rob Sargent
• Re: ALTER TEXT field to VARCHAR(1024)
  • From: John McKown
• Re: Postgre SQL SHA-256 Compliance
  • From: Stephen Frost
• Re: ALTER TEXT field to VARCHAR(1024)
  • From: Merlin Moncure
• Re: Postgre SQL SHA-256 Compliance
  • From: Merlin Moncure
• Re: Postgre SQL SHA-256 Compliance
  • From: Neil Tiffin
• Re: Postgre SQL SHA-256 Compliance
  • From: Paul Jungwirth
• Re: Postgre SQL SHA-256 Compliance
  • From: Albe Laurenz
• Re: Postgre SQL SHA-256 Compliance (UNCLASSIFIED)
  • From: Anthony Burden
• Re: Postgre SQL SHA-256 Compliance
  • From: Adrian Klaver
• Postgre SQL SHA-256 Compliance
  • From: Anthony Burden
• Re: Installing Postgresql on Linux Friendlyarm
  • From: Adrian Klaver
• Installing Postgresql on Linux Friendlyarm
  • From: Xiang Gan
• Re: Feature request: temporary schemas
  • From: Pete Hollobon
• Re: Detecting query timeouts properly
  • From: Albe Laurenz
• Re: a couple questions about convert()
  • From: smcg2297
• Re: unique index on embedded json object
  • From: Peter Geoghegan
• Re: unique index on embedded json object
  • From: John R Pierce
• unique index on embedded json object
  • From: Lee Jason
• Re: can't restore database created with pg_dump
  • From: Eric Smith
• Detecting query timeouts properly
  • From: Evan Martin
• Re: Strategy for moving a large DB to another machine with least possible down-time
  • From: Andy Colson
• Re: Strategy for moving a large DB to another machine with least possible down-time
  • From: Andreas Joseph Krogh
• Re: Strategy for moving a large DB to another machine with least possible down-time
  • From: Adrian Klaver
• Re: Strategy for moving a large DB to another machine with least possible down-time
  • From: Andreas Joseph Krogh
• Re: Strategy for moving a large DB to another machine with least possible down-time
  • From: Adrian Klaver
• Re: Strategy for moving a large DB to another machine with least possible down-time
  • From: Andreas Joseph Krogh
• Re: Strategy for moving a large DB to another machine with least possible down-time
  • From: Bill Moran
• Strategy for moving a large DB to another machine with least possible down-time
  • From: Andreas Joseph Krogh
• Re: cloning database
  • From: David G Johnston
• Re: can't restore database created with pg_dump
  • From: Adrian Klaver
• Re: cloning database
  • From: Philipp Kraus
• Re: can't restore database created with pg_dump
  • From: Adrian Klaver