- phrase search
- Re: proposal: Preference SQL
- Fwd: Re: Core team statement on replication in PostgreSQL
- Overhauling GUCS
- Sugestion: xpath
- Re: Core team statement on replication in PostgreSQL
- Shouldn't Natural JOINs Follow FK Constraints?
- Re: Sugestion: xpath
- Re: Shouldn't Natural JOINs Follow FK Constraints?
- Shouldn't Natural JOINs Follow FK Constraints?
- move hash_any from hash to utils
- Re: Change lock requirements for adding a trigger
- proposal: Preference SQL
- Re: Core team statement on replication in PostgreSQL
- Initial max_connections for initdb on FreeBSD.
- replication hooks
- Duplicate Key Error from ANALYZE
- When quality is a requirement
- Core team statement on replication in PostgreSQL
- Estimating recursive query cost
- [PERFORM] Memory question on win32 systems
- Catching exceptions from COPY
- [PERFORM] Memory question on win32 systems
- intercepting WAL writes
- Re: BUG #4204: COPY to table with FK has memory leak
- pg_regress: dbname in PostgreSQL test suite
- Upcoming back-branch update releases
- pg_regress: referencing shared objects from tests
- Avoiding second heap scan in VACUUM
- Add dblink function to check if a named connection exists
- Proposal - Collation at database level
- Hint Bits and Write I/O
- Hiding undocumented enum values?
- accessing functions in the core
- WITH RECURSIVE patches V0.1 TODO items
- Remove redundant extra_desc info for enum GUC variables?
- Re: Updated patch (Re: [PATCHES] WITH RECURSIVE patch V0.1)
- Help with new contrib
- Proposal: temporal extension "period" data type
- Read Uncommitted
- Packages in oracle Style
- Re: [PERFORM] Posible planner improvement?
- Does 'ALTER INDEX' take exclusive lock?
- DROP ROLE dependency tracking ...
- jordan shoes 30$, handbag 30$,free shipping ,help you to dropship,open the website to have a look at ,give me some comment
- Re: [GENERAL] Fragments in tsearch2 headline
- \df displaying volatility
- keyword list/ecpg
- Re: [GENERAL] Fragments in tsearch2 headline
- Random order of archiving files
- Execution-time-sensitive timestamp regression tests
- Re: [ADMIN] Error while executing pg_dump "invalid memory alloc request size 4294967293"
- why SPI_execute_with_args don't use known values for optimalisation
- May Commitfest is done!
- proposal: table functions and plpgsql
- plpgpsm future
- idea: storing view source in system catalogs
- plpgsql: penalty due to double evaluation of parameters
- Installation of Postgres 32Bit on 64 bit machine
- Installation of Postgres 32Bit on 64 bit machine
- DTrace probes.
- Re: WITH RECURSIVE patch V0.1
- triggers on prepare, commit, rollback... ?
- =?iso-8859-1?Q?Agro-annuaire.com_vous_invite_=E0_nous_rendre_visite_au _Sa?==?iso-8859-1?Q?lon_SMA-Med_Food_2008_du_20_au_24_mai?=
- ERRORDATA_STACK_SIZE panic crashes on Windows
- ignore $PostgreSQL lines in regression tests?
- notification information functions
- MY EMAIL LOSED
- New DTrace probes proposal
- Link requirements creep
- use of pager on Windows psql
- What in the world is happening on spoonbill?
- Problems with CVS HEAD compile
- windows builds hanging on regression checks
- Re: [GSoC08]some detail plan of improving hash index
- When quality is a requirement
- Re: [GSoC08]some detail plan of improving hash index
- deadlock while doing VACUUM and DROP
- SSL and USER_CERT_FILE patch
- SSL and USER_CERT_FILE round 2
- Adding variables for segment_size, wal_segment_size and block sizes
- SSL and USER_CERT_FILE
- Buildfarm: cardinal down for maintenance.
- Would like to sponsor implementation of MATERIALIZED VIEWS
- Confusing message in log file
- Can't t compile current HEAD
- Permissions restrictions for function call statistics?
- WAL file naming sequence definition
- [rfc,patch] PL/Proxy in core
- missing $PostgreSQL:$
- Placement for a /port sort of include file?
- What to do with inline warnings?
- Re: Execution Plan Cost
- CVS HEAD warnings fixed
- Re: [PATCHES] stored procedure stats in collector
- how to perform silent installation on linux and solaris
- psql \? help display
- Arbitary file size limit in twophase.c
- Problem returning strings with pgsql 8.3.x
- odd output in restore mode
- Fairly serious bug induced by latest guc enum changes
- Re: Proposal: Integrity check
- Syntax decisions for pl/pgsql RAISE extension
- Re: [COMMITTERS] pgsql: Convert wal_sync_method to guc enum.
- XIDs and big boxes again ...
- another ecpg crash
- Rethinking dependency traversal during DROP
- "Claimed" status on Commitfest pages
- ecpg crash
- Re: Deterministic locking in PostgreSQL
- Re: gsoc08, text search selectivity, pg_statistics holding an array of a different type
- bloated heapam.h
- psql wrapped format default for backslash-d commands
- Bug 3883 revisited
- Re: [COMMITTERS] pgsql: Improve logic for finding object files on OBJS lines in contrib
- Relatively simple question about getting attributes from the whereclause
- constraint exclusion analysis caching
- MSVC build broken
- Execution Plan Cost
- dbmirror - migration to 8.3 from 7.4
- Re: Proposal for db level triggers
- Re: Lazy constraints / defaults
- Re: minimal update
- Auto-updated fields
- Table inheritance surprise
- Re: [pgsql-hackers] Posting to hackers and patches lists [OT]
- Re: [pgsql-www] [ADMIN] 8.2.4 patches? (fwd)
- Commit fest going well
- Re: [0/4] Proposal of SE-PostgreSQL patches
- Posting to hackers and patches lists
- Behaviour of MERGE with complex Rules
- Re: [PATCHES] Testing pg_terminate_backend()
- CONSTROID syscache vs relcache flushes
- Re: [PATCHES] column level privileges
- alter + preserving dependencies
- Re: [GENERAL] psql \pset pager
- Exposing quals
- Query Hints? No thanks. Data hints?
- Re: [PATCHES] GUC parameter cursors_tuple_fraction
- statement timeout vs dump/restore
- VacAttrStatsP vs VacAttrStats * (typedef'ing pointer types)
- Re: [COMMITTERS] pgsql: Sigh ...
- Re: Protection from SQL injection
- ecpg issue - not sending datatype to the backend
- Re: ecpg localization
- GDB X Postgresql 8 - Failed to read a valid object file image from memory
- Let the commit fest begin!
- Odd timezone backend output
- TidScan needs handling of a corner cases
- Internal design of MERGE, with Rules
- pg_standby issue
- Re: Proposed patch - psql wraps at window width
- Re: [0/4] Proposal of SE-PostgreSQL patches
- Optimizer sorting an already sorted result
- Re: [COMMITTERS] pgsql: Remove typename from A_Const.
- Re: [DOCS] pg_total_relation_size() and CHECKPOINT
- table format specification
- Re: [COMMITTERS] pgsql: Increase the statement_timeout value used in the prepared_xacts
- Re: [COMMITTERS] pgsql: Add generate_subscripts, aseries-generation function which
- WANTED: VACUUM SUMMARY
- Protection from SQL injection
- PQexecPrepared with cursor to fetch single results
- SRF in SFRM_ValuePerCall mode
- quirk using 'ltree' module: paths ending with a dot result in cryptic error message
- Recent buildfarm failures involving statement_timeout
- Traveling this week
- Compiling trigger function with MinGW
- we don't have a bugzilla
- Proposed Patch - LDAPS support for servers on port 636 w/o TLS
- FSM fill ratio
- Re: [COMMITTERS] pgsql: Update: < * Allow adding enumeratedvalues to an existing
- Re: Proposed patch - psql wraps at window width
- Standard metadata queries
- hm, why isn't SGT in the default timezone abbreviations list?
- Is this TODO item done?
- Avoiding a needless failure of PITR
- libpq object hooks -- needs copy result
- Re: [GENERAL] I think this is a BUG?
- Proposed patch - psql wraps at window width
- pg_ctl do_restart
- [RFC] Localized literals
- RECORD.* doesn't work in Pl/PGSQL
- CommitFest Wiki page annoyance
- Per-table random_page_cost for tables that we know are always cached
- Can't start psql
- Problem with server/utils/snapmgr.h
- WIP: psql default banner patch
- MERGE Specification
- Commitfest namespacing (was: TODO, FAQs to Wiki?)
- pgstat SRF?
- port/thread.c and pthreads
- Regression test fails when BLCKSZ is 1kB
- hacinking network
- typedefs for indent
- log_filename()
- INSERT ... SELECT ... FOR SHARED?
- -DCLOBBER_CACHE_ALWAYS build takes far longer than before
- WAL files format
- pgkill on win32
- TODO.detail removed
- TODO, FAQs to Wiki?
- Re: [PATCHES] Coding standards
- Re: pgsql: Fix a couple of oversights associated with the "physical tlist"
- Plan targetlists in EXPLAIN output
- new field content lost
- Cross-field statistics
- Re: [COMMITTERS] pgsql: Repair two places where SIGTERM exit couldleave shared memory
- get rid of psql welcome message
- Timely reporting of COPY errors
- MERGE SQL Statement
- How to submit a patch
- /etc/init.d/postgresql status error
- Collation at database level
- Improving planner variable handling
- DROP DATABASE vs patch to not remove files right away
- Re: [SQL] rule for update view that updates/inserts into 2 tables
- Re: [PATCHES] Avahi support for Postgresql
- stack smashing detected
- pulling libpqtypes from queue
- Re: [COMMITTERS] pgsql: Add pg_terminate_backend() to allowterminating only a single
- WIP: Pg_upgrade - page layout converter (PLC) hook
- rule for update view that updates/inserts into 2 tables
- bug in localized \df+ output
- Lessons from commit fest
- pg_dump object sorting
- Race conditions in relcache load (again)
- proposal: Additional parameters for RAISE statement
- pgwin32_safestat weirdness
- Re: [Pljava-dev] stack depth limit exceeded - patch possible?
- Re: Patch to add objetct size on "\d+" verbose output
- stack depth limit exceeded - patch possible?
- runtime error on SPGIST, needed help
- Re: Cached Query Plans
- Re: Remove lossy-operator RECHECK flag?
- Re: Patch to add objetct size on "\d+" verbose output
- Commit fest status
- Remove lossy-operator RECHECK flag?
- Cached Query Plans (was: global prepared statements)
- stat() vs cygwin
- question on how to correctly communicate with external library functions which return malloc()'ed strings
- Re: none
- Dumb Micro-Optimization
- Index AM change proposals, redux
- Re: Segfault using heap_form_tuple
- Re: Segfault using heap_form_tuple
- Segfault using heap_form_tuple
- psql \du and \dg commands.
- SQL fast in PSQL, very slow using MS.NET driver
- Commit fest queue
- Re: [COMMITTERS] pgsql: Remove mention of theBerkeley origins of the alias "Postgres"