| Replied (other) | BUG #1584: undefined symbol _tas | about 21 years ago |
| Replied (other) | Unexpected behaviour of numeric datatype when mixed with,float4, domains and plpgsql variables | about 21 years ago |
| Replied (other) | BUG #1591: BETWEEN NULL AND NULL causes crash | about 21 years ago |
| Started thread | pgsql: Make constant-folding produce sane output for | about 21 years ago |
| Started thread | pgsql: Make constant-folding produce sane output for | about 21 years ago |
| Started thread | pgsql: Make constant-folding produce sane output for | about 21 years ago |
| Replied (other) | BUG #1590: Comparison Operation with Strings | about 21 years ago |
| Replied (other) | BUG #1592: "with hold" cursor problem | about 21 years ago |
| Replied (other) | BUG #1582: boolean DEFAULT TRUE results in FALSE for NULL values | about 21 years ago |
| Replied (other) | BUG #1577: round(dp) function does not round to nearest integer properly | about 21 years ago |
| Started thread | pgsql: Split out into a separate function the code in grouping_planner() | about 21 years ago |
| Started thread | pgsql: SQL functions returning pass-by-reference types were copying the | about 21 years ago |
| Started thread | pgsql: SQL functions returning pass-by-reference types were copying the | about 21 years ago |
| Replied (other) | static genericcostestimate | about 21 years ago |
| Replied (other) | Unicode problems on IRC | about 21 years ago |
| Replied (other) | Problems with Set Returning Functions (SRFs) | about 21 years ago |
| Replied (other) | Three-byte Unicode characters | about 21 years ago |
| Replied (other) | Unicode problems on IRC | about 21 years ago |
| Replied (other) | table and column information from cursor? | about 21 years ago |
| Replied (other) | create user with database and contrib | about 21 years ago |
| Replied (other) | Functionscan estimates | about 21 years ago |
| Replied (own) | Optimizing maximum/minimum queries (yet again) | about 21 years ago |
| Replied (own) | Optimizing maximum/minimum queries (yet again) | about 21 years ago |
| Replied (other) | DELETE ... USING | about 21 years ago |
| Replied (own) | Optimizing maximum/minimum queries (yet again) | about 21 years ago |
| Replied (other) | DELETE ... USING | about 21 years ago |
| Replied (other) | Functionscan estimates | about 21 years ago |
| Replied (own) | Optimizing maximum/minimum queries (yet again) | about 21 years ago |
| Replied (own) | Optimizing maximum/minimum queries (yet again) | about 21 years ago |
| Replied (own) | Optimizing maximum/minimum queries (yet again) | about 21 years ago |
| Started thread | Optimizing maximum/minimum queries (yet again) | about 21 years ago |
| Replied (other) | Can't install plpython on Windows 8.0 | about 21 years ago |
| Replied (other) | Can't install plpython on Windows 8.0 | about 21 years ago |
| Replied (other) | Index use with left join | about 21 years ago |
| Started thread | pgsql: If we're going to have a non-panic check for held_lwlocks[] | about 21 years ago |
| Replied (other) | Index use with left join | about 21 years ago |
| Replied (other) | prepared statements don't log arguments? | about 21 years ago |
| Replied (other) | Weird psql crash | about 21 years ago |
| Replied (other) | 8.0.2 bundled ... | about 21 years ago |
| Replied (other) | Weird psql crash | about 21 years ago |
| Started thread | pgsql: Use an always-there test, not an Assert, to check for overrun of | about 21 years ago |
| Replied (other) | Plan for relatively simple query seems to be very inefficient | about 21 years ago |
| Started thread | pgsql: Stamp 8.0.2. | about 21 years ago |
| Started thread | pgsql: Update and copy-edit release notes for 8.0.2. | about 21 years ago |
| Started thread | pgsql: Update and copy-edit release notes for 8.0.2. | about 21 years ago |
| Replied (other) | seg fault with tsearch2 | about 21 years ago |
| Replied (other) | seg fault with tsearch2 | about 21 years ago |
| Started thread | pgsql: Fix some issues with missing or too many newlines at end of file. | about 21 years ago |
| Started thread | pgsql: Allow plpgsql functions to omit RETURN command when the function | about 21 years ago |
| Replied (other) | Plan for relatively simple query seems to be very inefficient | about 21 years ago |
| Replied (other) | COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion | about 21 years ago |
| Replied (other) | 'now' runtime | about 21 years ago |
| Replied (other) | About index_build | about 21 years ago |
| Replied (other) | float conversion / presentation problem ? | about 21 years ago |
| Replied (other) | prepared statements don't log arguments? | about 21 years ago |
| Replied (other) | pgsql: Add a "USING" clause to DELETE, which is equivalent to the FROM | about 21 years ago |
| Replied (other) | float conversion / presentation problem ? | about 21 years ago |
| Replied (other) | Plan for relatively simple query seems to be very inefficient | about 21 years ago |
| Replied (other) | monitoring database activity on solaris | about 21 years ago |
| Replied (other) | Plan for relatively simple query seems to be very inefficient | about 21 years ago |
| Replied (other) | Big trouble with memory !! | about 21 years ago |
| Replied (other) | COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion | about 21 years ago |
| Replied (other) | monitoring database activity on solaris | about 21 years ago |
| Replied (other) | Plan for relatively simple query seems to be very inefficient | about 21 years ago |
| Replied (other) | Plan for relatively simple query seems to be very inefficient | about 21 years ago |
| Replied (other) | lower function | about 21 years ago |
| Replied (other) | Big trouble with memory !! | about 21 years ago |
| Replied (other) | Problems with Set Returning Functions (SRFs) | about 21 years ago |
| Started thread | pgsql: Remove test for NULL node in ExecProcNode(). | about 21 years ago |
| Replied (other) | Plan for relatively simple query seems to be very inefficient | about 21 years ago |
| Replied (other) | very slow after a while... | about 21 years ago |
| Replied (other) | Big trouble with memory !! | about 21 years ago |
| Replied (other) | Big trouble with memory !! | about 21 years ago |
| Replied (other) | What encoding to use for this error? | about 21 years ago |
| Started thread | pgsql: Merge Resdom nodes into TargetEntry nodes to simplify code and | about 21 years ago |
| Replied (other) | BUG #1583: Locale problem | about 21 years ago |
| Started thread | Call for objections: merge Resdom with TargetEntry | about 21 years ago |
| Replied (other) | REINDEX ALL | about 21 years ago |
| Replied (other) | change attnum in pg_catalog.pg_attribute | about 21 years ago |
| Replied (other) | Check for existence of index | about 21 years ago |
| Replied (other) | change attnum in pg_catalog.pg_attribute | about 21 years ago |
| Started thread | pgsql: Adjust grammar for plpgsql's OPEN command so that a cursor can be | about 21 years ago |
| Replied (own) | Re: Vacuum time degrading | about 21 years ago |
| Replied (own) | Re: Vacuum time degrading | about 21 years ago |
| Replied (other) | Postmaster running out of discspace; Data corruption? | about 21 years ago |
| Replied (other) | plPHP in core? | about 21 years ago |
| Replied (other) | plPHP in core? | about 21 years ago |
| Replied (own) | Should we still require RETURN in plpgsql? | about 21 years ago |
| Replied (own) | Should we still require RETURN in plpgsql? | about 21 years ago |
| Replied (other) | plPHP in core? | about 21 years ago |
| Replied (other) | installation AIX - LINUX | about 21 years ago |
| Replied (other) | plPHP in core? | about 21 years ago |
| Replied (own) | Should we still require RETURN in plpgsql? | about 21 years ago |
| Started thread | Should we still require RETURN in plpgsql? | about 21 years ago |
| Started thread | pgsql: plpgsql does OUT parameters, as per my proposal a few weeks ago. | about 21 years ago |
| Replied (other) | Regarding niladic functions | about 21 years ago |
| Replied (other) | DELETE ... USING | about 21 years ago |
| Started thread | pgsql: Fix broken markup. | about 21 years ago |
| Replied (other) | DELETE ... USING | about 21 years ago |
| Replied (other) | plPHP in core? | about 21 years ago |
| Replied (other) | plPHP in core? | about 21 years ago |
| Replied (other) | plPHP in core? | about 21 years ago |
| Replied (other) | plPHP in core? | about 21 years ago |
| Replied (other) | DELETE ... USING | about 21 years ago |
| Replied (other) | DELETE ... USING | about 21 years ago |
| Replied (other) | invalid input syntax for type bytea | about 21 years ago |
| Replied (other) | field definitions in view results? | about 21 years ago |
| Started thread | Re: Vacuum time degrading | about 21 years ago |
| Replied (other) | BuildFarm status: recent check failures | about 21 years ago |
| Replied (other) | BuildFarm status: recent check failures | about 21 years ago |
| Replied (other) | Postgres mystery | about 21 years ago |
| Started thread | pgsql: In cost_mergejoin, the early-exit effect should not apply to the | about 21 years ago |
| Started thread | pgsql: In cost_mergejoin, the early-exit effect should not apply to the | about 21 years ago |
| Started thread | pgsql: In cost_mergejoin, the early-exit effect should not apply to the | about 21 years ago |
| Replied (other) | Bad mis-costing of Merge Left Join in 8.0.1 | about 21 years ago |
| Replied (other) | Strange plpgsql performance -- arithmetic, numeric() type, arrays | about 21 years ago |
| Replied (other) | Strange plpgsql performance -- arithmetic, numeric() type, arrays | about 21 years ago |
| Replied (other) | Postgres mystery | about 21 years ago |