Filter:

Messages in April 2018

Threads91 messages
25Started
3Replied in own
63Replied to othersin 25 threads
Patchesof which 1 carried a patch
0New patchfirst in its thread
1Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)documentation is now XMLabout 8 years ago
Replied (other)Postgres, fsync, and OSs (specifically linux)about 8 years ago
Replied (other)Postgres, fsync, and OSs (specifically linux)about 8 years ago
Replied (other)Can PostgreSQL create new WAL files instead of reusing old ones?about 8 years ago
Replied (other)documentation is now XMLabout 8 years ago
Replied (other)Appendix A. PostgreSQL Error Codesabout 8 years ago
Replied (other)Wrong exampleabout 8 years ago
Replied (other)pg_trgm word_similarity inconsistencies or bugover 8 years ago
Started threadpgsql: C comment: add description of root_tuple_slotover 8 years ago
Replied (other)description of root_tuple_slot missingover 8 years ago
Replied (other)Pgadmin III is officially not supportedover 8 years ago
Started threadpgsql: docs: remove "III" version text from pgAdmin linkover 8 years ago
Started threadpgsql: docs: remove "III" version text from pgAdmin linkover 8 years ago
Started threadpgsql: docs: remove "III" version text from pgAdmin linkover 8 years ago
Started threadpgsql: docs: remove "III" version text from pgAdmin linkover 8 years ago
Started threadpgsql: docs: remove "III" version text from pgAdmin linkover 8 years ago
Started threadpgsql: docs: remove "III" version text from pgAdmin linkover 8 years ago
Replied (other)how does jsonb_set work?over 8 years ago
Replied (other)Bugs in TOAST handling, OID assignment and redo recoveryover 8 years ago
Replied (other)Builtin connection pollingover 8 years ago
Replied (other)Builtin connection pollingover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)Builtin connection pollingover 8 years ago
Replied (other)documentation is now XMLover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (own)'make check' failsover 8 years ago
Replied (own)'make check' failsover 8 years ago
Replied (own)'make check' failsover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Started thread'make check' failsover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PATCH: multivariate histograms and MCV listsover 8 years ago
Replied (other)pgsql: New files for MERGEover 8 years ago
Replied (other)PATCH: multivariate histograms and MCV listsover 8 years ago
Replied (other)pgsql: New files for MERGEover 8 years ago
Replied (other)PgUpgrade bumped my XIDs by ~50M?over 8 years ago
Replied (other)pgsql: New files for MERGEover 8 years ago
Replied (other)Dead link in ltree documentationover 8 years ago
Started threadpgsql: doc: remove mention of the DMOZ catalog in ltree docsover 8 years ago
Started threadpgsql: doc: remove mention of the DMOZ catalog in ltree docsover 8 years ago
Started threadpgsql: doc: remove mention of the DMOZ catalog in ltree docsover 8 years ago
Started threadpgsql: doc: remove mention of the DMOZ catalog in ltree docsover 8 years ago
Started threadpgsql: doc: remove mention of the DMOZ catalog in ltree docsover 8 years ago
Started threadpgsql: doc: remove mention of the DMOZ catalog in ltree docsover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PgUpgrade bumped my XIDs by ~50M?over 8 years ago
Replied (other)PgUpgrade bumped my XIDs by ~50M?over 8 years ago
Replied (other)Dead link in ltree documentationover 8 years ago
Started threadpgsql: docs: update ltree URL for the DMOZ catalogover 8 years ago
Started threadpgsql: docs: update ltree URL for the DMOZ catalogover 8 years ago
Started threadpgsql: docs: update ltree URL for the DMOZ catalogover 8 years ago
Started threadpgsql: docs: update ltree URL for the DMOZ catalogover 8 years ago
Started threadpgsql: docs: update ltree URL for the DMOZ catalogover 8 years ago
Started threadpgsql: docs: update ltree URL for the DMOZ catalogover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)Extra comma in documentation of array_fillover 8 years ago
Replied (other)Comment update in BuildTupleFromCStrings()over 8 years ago
Started threadpgsql: C comment: mention null handling in BuildTupleFromCStrings()over 8 years ago
Replied (other)BUG #15122: can't import data if table has a constraint with a function calling another functionover 8 years ago
Replied (other)jsonb nesting level edge caseover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)float and float(p) missing from table 8.1over 8 years ago
Replied (other)Synopsis of SELECT statement: UNION, INTERSECTION, EXCEPTover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)2018-03 Commitfest Summary (Andres #1)over 8 years ago
Replied (other)Follow-up patchSynopsis of SELECT statement: UNION, INTERSECTION, EXCEPTover 8 years ago
Replied (other)"IS NOT DOCUMENT" is missingover 8 years ago
Started threadpgsql: doc: document "IS NOT DOCUMENT"over 8 years ago
Started threadpgsql: doc: document "IS NOT DOCUMENT"over 8 years ago
Started threadpgsql: doc: document "IS NOT DOCUMENT"over 8 years ago
Started threadpgsql: doc: document "IS NOT DOCUMENT"over 8 years ago
Replied (other)BUG #15112: Unable to run pg_upgrade with earthdistance extensionover 8 years ago