- Re: [PATCHES] problem with CR+LF in files in psql \i command
- understanding pg_stat* numbers
- Re: [COMMITTERS] pgsql: Fix two bugs in change_owner_recurse_to_sequences:
- 8.0.2beta1 ... look her over ...
- Re: Patch for collation using ICU
- Re: Patch for collation using ICU
- Re: Patch for collation using ICU
- Missing segment 3 of index
- minor windows & cygwin regression failures on stable branch
- HeapTupleSatisfiesUpdate missing a bet?
- Re: lazy_update_relstats considered harmful (was Re: [PERFORM]
- Re: lazy_update_relstats considered harmful (was Re: [PERFORM]
- Bug 1500
- Re: Patch for collation using ICU
- Re: Patch for collation using ICU
- pg_dump issue : Cannot drop a non-existent(?) trigger
- Re: Upcoming 8.0.2 Release
- Re: Patch for collation using ICU
- Installation docs wrong?
- Calling Functions from Delete Rule (+ contrib/pgcrypto) = madness??
- Patch for collation using ICU
- Re: Upcoming 8.0.2 Release
- Re: Upcoming 8.0.2 Release
- Re: Upcoming 8.0.2 Release
- Functions + plpgsql + contrib/pgcrypto = ??
- Upcoming 8.0.2 Release
- Re: RFC: built-in historical query time profiling
- Postgres recoverey for deleted row of data
- RFC: built-in historical query time profiling
- more detailed timing ?
- help with corrupted database
- Re: locks in CREATE TRIGGER, ADD FK
- \x in psql
- Re: WAL: O_DIRECT and multipage-writer
- Another history question
- odd problem !
- Permissions on tables and views
- Failed to re-find parent key
- Re: what to do with backend flowchart
- problem with rules - column values lost
- locks in CREATE TRIGGER, ADD FK
- Using new copy libpq functions on a v2 protocol backend
- psql and pg_dump using obselete copy commands
- Proposal: OUT parameters for plpgsql
- Prevent conflicting SET options from being set
- custome exception handling support ?
- [Mail Delivery System <Mailer-Daemon@xeocode.com>] Warning: message 1DAroW-0002DC-00 delayed 144 hours
- what to do with backend flowchart
- Moving a project from gborg to pgfoundry?
- Re: [pgsql-hackers-win32] snprintf causes regression tests
- Avoiding unnecessary writes during relation drop and truncate
- Very strange query difference between 7.3.6 and 7.4.6 (7.3.6 kicking7.4.6 butt)
- GUC variable for setting number of local buffers
- rewriter in updateable views
- Re: [pgsql-www] "they only drink coffee at dec"
- Re: "they only drink coffee at dec"
- Re: securing pg_proc
- QueryResults from Executor
- Version 1.0.0.18 of OLE DB released
- Unstable timestamp binary representation?
- "they only drink coffee at dec"
- read-only planner input
- Query crashes/hangs server
- corrupted tuple (header?), pg_filedump output
- Re:
- depended on table types
- Lockfile restart failure is still there :-(
- Re: [pgsql-hackers-win32] win32 performance - fsync question
- Windows, gettext/libintl, pg_sprintf and friends
- Re: [pgsql-hackers-win32] win32 performance - fsync question
- Re: securing pg_proc
- Re: securing pg_proc
- securing pg_proc
- Re: Changing the default wal_sync_method to open_sync for
- Re: Changing the default wal_sync_method to open_sync for Win32?
- Re: [pgsql-hackers-win32] win32 performance - fsync question
- Re: Changing the default wal_sync_method to open_sync for Win32?
- Exception handiling
- WIN1252 patch broke my database
- Savepoints and SPI
- Re: PQexecParams
- contrib/pgcrypto
- Re: PQexecParams
- Re: caches lifetime with SQL vs PL/PGSQL procs
- read-only database
- Erratic error message "ERROR: column "id_compte" does not exist"
- Real-Time Vacuum Possibility
- contrib/pg_buffercache
- change palloc to malloc
- CVS head broken on win32?
- Re: type unknown - how important is it?
- PHP stuff
- PQexecParams
- Avoiding tuple construction/deconstruction during joining
- options in conninfo
- invalidating cached plans
- signed short fd
- Null Value Stored for Date e TimeStamp
- where is the locale set for each server instance?
- Re: [PERFORM] How to read query plan
- materialized views
- Re: date_trunc problem in HEAD
- Question about encoding combinations
- Strange postgres planner behaviour
- REL8_0_STABLE and 8.0.1 release client logging difference
- cvsup binaries?
- Re: partial vacuum
- Re: Bumping libpq version number?
- Re: [PATCHES] BUG #1466: syslogger issues
- Re: Bumping libpq version number?
- Re: Bumping libpq version number?
- Bumping libpq version number?
- Re: Grant ALL on schema
- Explain Analyze mode
- PostgreSQL pam ldap document
- Re: We are not following the spec for HAVING without GROUP BY
- Re: Raw size
- Re: We are not following the spec for HAVING without GR
- Raw size
- Re: [ADMIN] Too frequent warnings for wraparound failure
- TODO item: support triggers on columns
- Re: We are not following the spec for HAVING without GROUP BY
- NIST Test Suite
- Re: We are not following the spec for HAVING without GROUP
- Information schema tweak?
- Re: could not read, could not write, could not fsync, Windows 2000, PostgreSQL 8.0.1
- Re: BUG #1528: Rows returned that should be excluded by WHERE clause
- Runtime accepting build discrepancies
- Re: fool-toleranced optimizer
- pgpool question
- Current CVS parallel test lock
- two questions related to tablespace in PG8.0.1
- fool-toleranced optimizer
- Re: How to cast VARCHAR to BYTEA and vice-versa?
- How to cast VARCHAR to BYTEA and vice-versa?
- ERROR: unrecognized node type in PostgresMain( )
- Re: A bad plan
- Indicies work on FreeBSD, not on Linux
- Best practices: MERGE
- A bad plan
- One vacuum full is not enough.
- Recording vacuum/analyze/dump times
- anoncvs unreachable?
- get generated keys and insert returning
- Re: Cost of XLogInsert CRC calculations
- Re: buildfarm issues
- ERROR: unrecognized node type in PostgresMain( )
- About b-tree usage
- Re: Implementation of SQLCODE and SQLERRM variables for PL/pgSQL
- Speeding up tupledesc copying
- Re: refactoring fork() and EXEC_BACKEND
- Missing coalesce
- Cost of XLogInsert CRC calculations
- Explicit Transaction Priority
- Manual vs automatic functionality
- Exception ERROR Code
- buildfarm issues
- I am in Copenhagen
- db cluster ?
- Re: refactoring fork() and EXEC_BACKEND
- postgreSQL-8.0.1 configure --enable-thread-safety with icc-8.1 on RHEL-AS3 Itanium-2 gives error
- refactoring fork() and EXEC_BACKEND
- Solving hash table overrun problems
- one vacuum full is not enough ?
- Re: unexpected and reproducable crash in pl/pgsql function
- Re: unexpected and reproducable crash in pl/pgsql function
- Re: logging as inserts
- plperl function has side-effects
- consequent btree index scans optimizations ?
- cluster table by two-column index ?
- postgreSQL-8.0.1 compilation with icc-8.1 on Itanium-2 gives "error: asm statements not supported"
- Re: 8.0.X and the ARC patent
- Doc correction
- hi all
- Re: [pgsql-hackers-win32] snprintf causes regression tests
- Re: Development Plans
- Re: snprintf causes regression tests to fail
- Re: [pgsql-hackers-win32] snprintf causes regression tests to fail
- logging as inserts
- Re: [pgsql-hackers-win32] snprintf causes regression tests to fail
- Re: Where to see the patch queue (was Re: [PATCHES] Patch for Postmaster
- index file detached from data file
- hsl
- Re: SQL99 Hierarchical queries
- mysterious log output
- Re: snprintf causes regression tests to fail
- Re: [pgsql-advocacy] Development Plans
- Execute and PortalSuspended needs explicit transaction to work?
- Re: [PATCHES] snprintf causes regression tests to fail
- Re: SQL99 Hierarchical queries
- bitmap AM design
- Re: [pgsql-hackers-win32] win32 performance - fsync question
- serial as FK ?
- Re: serial as FK ?
- Re: Problems With PGAdmin
- Re: snprintf causes regression tests to fail
- Re: serial as FK ?
- Re: [pgsql-advocacy] Development Plans
- Re: SQL99 Hierarchical queries
- snprintf causes regression tests to fail
- Re: [pgsql-hackers-win32] win32 performance - fsync question
- Re: win32 performance - fsync question
- Re: win32 performance - fsync question
- Re: idea for concurrent seqscans
- Modifying COPY TO
- CAN-2005-0247
- Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
- Re: [JDBC] Where are we on stored procedures?
- Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
- Re: [pgsql-hackers] Daily digest v1.4988 (21 messages)
- Re: [pgsql-advocacy] Development Plans
- Re: Development Plans
- Re: Development Plans
- Re: Interesting NetBSD annual report
- Re: Where are we on stored procedures?
- Re: [pgsql-hackers-win32] win32 performance - fsync question
- idea for concurrent seqscans
- Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
- Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
- Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
- Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
- Re: Some download statistics
- Re: Some download statistics
- Re: [pgsql-hackers-win32] win32 performance - fsync question
- Re: [pgsql-hackers-win32] win32 performance - fsync question
- Re: [ADMIN] invalid multibyte character for locale
- Some download statistics
- Re: [pgsql-hackers-win32] win32 performance - fsync question
- Re: [pgsql-hackers-win32] win32 performance - fsync question
- Re: SQL99 Hierarchical queries
- Finding if old transactions are running...
- Finding if old transactions are running...
- problem with function loading
- Re: Question on TRUNCATE privleges
- Re: [NOVICE] Question on TRUNCATE privleges
- Cannot link to postgres 8.0.0 databases using ODBC from Access
- Re: [PATCHES] [pgsql-hackers-win32] Repleacement for src/port/snprintf.c
- Postgres on VXworks+SH4
- Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
- big problem
- Question about "Unrecognized SPI code" ...
- int64/double for time/timestamp
- psql: recall previous command?
- left-deep plans?
- Re: sigint psql
- Re: sigint psql
- Re: win32 performance - fsync question
- Re: win32 performance - fsync question
- slow mail server ?
- Transaction Aborted