| Replied (other) | Generating GRANT/REVOKE on functions from catalog | about 17 years ago |
| Replied (other) | head contrib is broken (crypto) | about 17 years ago |
| Replied (other) | the case for machine-readable error fields | about 17 years ago |
| Replied (other) | Generating GRANT/REVOKE on functions from catalog | about 17 years ago |
| Started thread | pgsql: Fix pg_dump to do the right thing when escaping the contents of | about 17 years ago |
| Replied (other) | the case for machine-readable error fields | about 17 years ago |
| Started thread | pgsql: Fix an ecpg test, too. | about 17 years ago |
| Replied (other) | Executor Material | about 17 years ago |
| Replied (own) | pg_dump vs PQescapeBytea | about 17 years ago |
| Replied (other) | the case for machine-readable error fields | about 17 years ago |
| Started thread | pgsql: Fix some more regression tests (missed these because they're only | about 17 years ago |
| Replied (other) | the case for machine-readable error fields | about 17 years ago |
| Started thread | pgsql: Suppress pointer-signedness warning. | about 17 years ago |
| Replied (other) | CHECK constraint fails when it's not supposed to | about 17 years ago |
| Started thread | pgsql: Ooops, missed that a couple of contrib modules have calls to | about 17 years ago |
| Replied (other) | the case for machine-readable error fields | about 17 years ago |
| Started thread | pgsql: Teach PQescapeByteaConn() to use hex format when the target | about 17 years ago |
| Started thread | pg_dump vs PQescapeBytea | about 17 years ago |
| Replied (other) | bytea vs. pg_dump | about 17 years ago |
| Replied (other) | bytea vs. pg_dump | about 17 years ago |
| Started thread | pgsql: Support hex-string input and output for type BYTEA. | about 17 years ago |
| Replied (other) | Alpha Releases: Docs? | about 17 years ago |
| Replied (other) | Alpha Releases: Docs? | about 17 years ago |
| Replied (other) | Proposal: More portable way to support 64bit platforms | about 17 years ago |
| Replied (own) | pgsql: Cause pg_proc.probin to be declared as text, not bytea. | about 17 years ago |
| Replied (other) | parameters in functions and overlap with names of columns | about 17 years ago |
| Replied (other) | Proposal: More portable way to support 64bit platforms | about 17 years ago |
| Replied (other) | Alpha Releases: Docs? | about 17 years ago |
| Replied (other) | Review: Revise parallel pg_restore's scheduling heuristic | about 17 years ago |
| Replied (other) | bytea vs. pg_dump | about 17 years ago |
| Replied (other) | bytea vs. pg_dump | about 17 years ago |
| Replied (other) | Re: async notification patch for dblink | about 17 years ago |
| Replied (own) | pg_proc.probin should become text? | about 17 years ago |
| Replied (other) | doing %-expansion in plpgsql RAISE USING | about 17 years ago |
| Replied (own) | pgsql: Cause pg_proc.probin to be declared as text, not bytea. | about 17 years ago |
| Replied (other) | SE-PostgreSQL Specifications | about 17 years ago |
| Replied (other) | Refer to another database | about 17 years ago |
| Replied (own) | pg_proc.probin should become text? | about 17 years ago |
| Replied (other) | Refer to another database | about 17 years ago |
| Started thread | pgsql: Cause pg_proc.probin to be declared as text, not bytea. | about 17 years ago |
| Replied (other) | WIP: to_char, support for EEEE format | about 17 years ago |
| Replied (own) | pg_proc.probin should become text? | about 17 years ago |
| Replied (other) | WIP: to_char, support for EEEE format | about 17 years ago |
| Replied (other) | Re: async notification patch for dblink | about 17 years ago |
| Replied (other) | Re: async notification patch for dblink | about 17 years ago |
| Started thread | pg_proc.probin should become text? | about 17 years ago |
| Replied (other) | bytea vs. pg_dump | about 17 years ago |
| Replied (other) | bytea vs. pg_dump | about 17 years ago |
| Replied (other) | bytea vs. pg_dump | about 17 years ago |