| Replied (other) | Function returning 2 columns evaluated twice when both columns are needed | almost 17 years ago |
| Replied (own) | Boosting cost estimates for some built-in functions | almost 17 years ago |
| Replied (own) | Controlling changes in plpgsql variable resolution | almost 17 years ago |
| Replied (other) | LATERAL | almost 17 years ago |
| Started thread | Boosting cost estimates for some built-in functions | almost 17 years ago |
| Started thread | Controlling changes in plpgsql variable resolution | almost 17 years ago |
| Replied (other) | Determining dead/unused space in a table? | almost 17 years ago |
| Replied (other) | LATERAL | almost 17 years ago |
| Replied (other) | LATERAL | almost 17 years ago |
| Replied (other) | LATERAL | almost 17 years ago |
| Replied (other) | Deprecation | almost 17 years ago |
| Replied (other) | Deprecation | almost 17 years ago |
| Replied (other) | Deprecation | almost 17 years ago |
| Replied (other) | Problem with using snprintf in C-function | almost 17 years ago |
| Replied (other) | pgsql2shp : Encoding headache | almost 17 years ago |
| Started thread | pgsql: Rewrite pam_passwd_conv_proc to be more robust: avoid assuming | almost 17 years ago |
| Started thread | pgsql: Rewrite pam_passwd_conv_proc to be more robust: avoid assuming | almost 17 years ago |
| Started thread | pgsql: Rewrite pam_passwd_conv_proc to be more robust: avoid assuming | almost 17 years ago |
| Started thread | pgsql: Rewrite pam_passwd_conv_proc to be more robust: avoid assuming | almost 17 years ago |
| Started thread | pgsql: Rewrite pam_passwd_conv_proc to be more robust: avoid assuming | almost 17 years ago |
| Started thread | pgsql: Rewrite pam_passwd_conv_proc to be more robust: avoid assuming | almost 17 years ago |
| Started thread | pgsql: Rewrite pam_passwd_conv_proc to be more robust: avoid assuming | almost 17 years ago |
| Replied (other) | BUG #5121: Segmentation Fault when using pam w/ krb5 | almost 17 years ago |
| Replied (own) | Getting the red out (of the buildfarm) | almost 17 years ago |
| Replied (other) | Deprecation | almost 17 years ago |
| Replied (own) | Getting the red out (of the buildfarm) | almost 17 years ago |
| Replied (other) | BUG #5121: Segmentation Fault when using pam w/ krb5 | almost 17 years ago |
| Replied (other) | [PATCH] Reworks for Access Control facilities (r2350) | almost 17 years ago |
| Replied (other) | BUG #5123: bug in window function "last_value" | almost 17 years ago |
| Replied (other) | Deprecation | almost 17 years ago |
| Replied (other) | BUG #5121: Segmentation Fault when using pam w/ krb5 | almost 17 years ago |
| Replied (other) | BUG #5121: Segmentation Fault when using pam w/ krb5 | almost 17 years ago |
| Replied (other) | BUG #5121: Segmentation Fault when using pam w/ krb5 | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | BUG #5118: start-status-insert-fatal | almost 17 years ago |
| Replied (other) | BUG #5118: start-status-insert-fatal | almost 17 years ago |
| Replied (other) | Trigger with WHEN clause (WIP) | almost 17 years ago |
| Replied (other) | BUG #5121: Segmentation Fault when using pam w/ krb5 | almost 17 years ago |
| Replied (other) | WIP: generalized index constraints | almost 17 years ago |
| Replied (other) | Wrong estimation of rows for hash join | almost 17 years ago |
| Replied (other) | savepoint name vs prepared transaction name | almost 17 years ago |
| Replied (other) | Trigger with WHEN clause (WIP) | almost 17 years ago |
| Replied (other) | Trigger with WHEN clause (WIP) | almost 17 years ago |
| Replied (other) | BUG #5123: bug in window function "last_value" | almost 17 years ago |
| Replied (other) | BUG #5122: Subqueries - inner select statement bug | almost 17 years ago |
| Replied (other) | inefficient use of relation extension? | almost 17 years ago |
| Started thread | pgsql: First committed version of plpython_unicode_0.out did not | almost 17 years ago |
| Replied (other) | BUG #5121: Segmentation Fault when using pam w/ krb5 | almost 17 years ago |
| Replied (other) | Craeteing sparse arrays | almost 17 years ago |
| Replied (other) | inefficient use of relation extension? | almost 17 years ago |
| Replied (other) | Re: BUG #5120: Performance difference between running a query with named cursor and straight SELECT | almost 17 years ago |
| Replied (other) | BUG #5121: Segmentation Fault when using pam w/ krb5 | almost 17 years ago |
| Replied (other) | Re: BUG #5120: Performance difference between running a query with named cursor and straight SELECT | almost 17 years ago |
| Replied (other) | BUG #5118: start-status-insert-fatal | almost 17 years ago |
| Replied (other) | BUG #5118: start-status-insert-fatal | almost 17 years ago |
| Replied (other) | Postgresql 8.4.1 segfault, backtrace | almost 17 years ago |
| Replied (other) | BUG #5118: start-status-insert-fatal | almost 17 years ago |
| Replied (other) | BUG #5118: start-status-insert-fatal | almost 17 years ago |
| Replied (other) | BUG #5120: Performance difference between running a query with named cursor and straight SELECT | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | BUG #5118: start-status-insert-fatal | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | BUG #5118: start-status-insert-fatal | almost 17 years ago |
| Replied (other) | [PATCH] Reworks for Access Control facilities (r2350) | almost 17 years ago |
| Replied (other) | Client application name | almost 17 years ago |
| Replied (other) | BUG #5118: start-status-insert-fatal | almost 17 years ago |
| Replied (other) | SFPUG: Video from "Statistics and Postgres -- How the Planner Sees Your Data" Now on Vimeo | almost 17 years ago |
| Replied (other) | Client application name | almost 17 years ago |
| Replied (other) | Buffer usage in EXPLAIN and pg_stat_statements (review) | almost 17 years ago |
| Replied (other) | Trigger with WHEN clause (WIP) | almost 17 years ago |
| Replied (other) | Client application name | almost 17 years ago |
| Replied (other) | Can't find documentation for ~=~ operator | almost 17 years ago |
| Replied (other) | Trigger with WHEN clause (WIP) | almost 17 years ago |
| Replied (other) | Client application name | almost 17 years ago |
| Replied (other) | Could regexp_matches be immutable? | almost 17 years ago |
| Replied (other) | Could regexp_matches be immutable? | almost 17 years ago |
| Replied (other) | [PATCH] Reworks for Access Control facilities (r2350) | almost 17 years ago |
| Replied (other) | BUG #5116: could not determine encoding for locale | almost 17 years ago |
| Replied (other) | What does this configure warning mean? | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | Triggers on columns | almost 17 years ago |
| Started thread | pgsql: Support SQL-compliant triggers on columns, ie fire only if | almost 17 years ago |
| Replied (other) | Could regexp_matches be immutable? | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | Could regexp_matches be immutable? | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | What does this configure warning mean? | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | Triggers on columns | almost 17 years ago |
| Replied (other) | Client application name | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | Kerberos authentication, Active Directory, and PostgreSQL | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | [PATCH] Largeobject access controls | almost 17 years ago |
| Replied (other) | BUG #5115: ADD UNIQUE table_constraint with expression | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | BUG #5115: ADD UNIQUE table_constraint with expression | almost 17 years ago |
| Replied (other) | Rejecting weak passwords | almost 17 years ago |
| Replied (other) | COPY BINARY 8.3 to 8.4 timestamp incorrect | almost 17 years ago |
| Replied (other) | Client application name | almost 17 years ago |
| Replied (other) | different sort order for primary key index | almost 17 years ago |
| Replied (other) | COPY BINARY 8.3 to 8.4 timestamp incorrect | almost 17 years ago |
| Replied (other) | Buffer usage in EXPLAIN and pg_stat_statements (review) | almost 17 years ago |
| Replied (other) | [PATCH] Largeobject access controls | almost 17 years ago |
| Replied (other) | Client application name | almost 17 years ago |
| Replied (other) | Unicode UTF-8 table formatting for psql text output | almost 17 years ago |
| Started thread | pgsql: Add "\pset linestyle ascii/unicode" option to psql, allowing our | almost 17 years ago |
| Replied (other) | Client application name | almost 17 years ago |
| Replied (other) | Possible encoding issue (win7) | almost 17 years ago |
| Replied (other) | Kerberos authentication, Active Directory, and PostgreSQL | almost 17 years ago |
| Replied (other) | Wire protocol docs | almost 17 years ago |
| Replied (other) | Client application name | almost 17 years ago |
| Replied (other) | COPY enhancements | almost 17 years ago |
| Replied (other) | Client application name | almost 17 years ago |
| Replied (other) | Client application name | almost 17 years ago |
| Replied (other) | Client application name | almost 17 years ago |
| Replied (other) | Buffer usage in EXPLAIN and pg_stat_statements (review) | almost 17 years ago |
| Replied (own) | EvalPlanQual seems a tad broken | almost 17 years ago |
| Replied (other) | COPY enhancements | almost 17 years ago |
| Started thread | pgsql: Fix ts_stat's failure on empty tsvector. | almost 17 years ago |
| Started thread | pgsql: Fix ts_stat's failure on empty tsvector. | almost 17 years ago |
| Replied (other) | BUG #5111: Segmentation fault, if to_tsvector returns empty row to ts_stat | almost 17 years ago |
| Replied (other) | Kerberos authentication, Active Directory, and PostgreSQL | almost 17 years ago |
| Replied (other) | CTE bug? | almost 17 years ago |
| Replied (other) | BUG #5108: plpgsql function name conflict with table alias | almost 17 years ago |
| Started thread | pgsql: Code review for LIKE INCLUDING patch --- clean up some cosmetic | almost 17 years ago |
| Replied (other) | GRANT ON ALL IN schema | almost 17 years ago |
| Started thread | pgsql: Use plurals (TABLES, FUNCTIONS, etc) in ALTER DEFAULT PRIVILEGES. | almost 17 years ago |
| Replied (other) | GRANT ON ALL IN schema | almost 17 years ago |
| Started thread | pgsql: Support GRANT/REVOKE ON ALL TABLES/SEQUENCES/FUNCTIONS IN SCHEMA. | almost 17 years ago |
| Replied (own) | EvalPlanQual seems a tad broken | almost 17 years ago |
| Replied (other) | GRANT ON ALL IN schema | almost 17 years ago |
| Started thread | pgsql: Move the handling of SELECT FOR UPDATE locking and rechecking out | almost 17 years ago |
| Replied (own) | Is FOR UPDATE an optimization fence? | almost 17 years ago |
| Replied (other) | ERROR: simple_heap_delete: tuple already updated by self | almost 17 years ago |
| Started thread | EvalPlanQual seems a tad broken | almost 17 years ago |
| Replied (other) | BUG #5108: plpgsql function name conflict with table alias | almost 17 years ago |
| Replied (other) | Dumping without Postgis functions | almost 17 years ago |
| Replied (other) | Where can I get the number of plans that considered by Planner? | almost 17 years ago |
| Replied (other) | man pages | almost 17 years ago |