Re: [DOCS] PATCH: Warn users about tablespace abuse data loss risk

2014-02-12 15:16 GMT+09:00 Ian Lawrence Barwick : > 2014-02-12 14:06 GMT+09:00 David Johnston : >> Ian Lawrence Barwick wrote >>> 2014-02-12 12:52 GMT+09:00 Craig Ringer < >> >>> craig@ >> >>> >: >>>> Hi all &

Re: [DOCS] PATCH: Warn users about tablespace abuse data loss risk

2014-02-12 14:06 GMT+09:00 David Johnston : > Ian Lawrence Barwick wrote >> 2014-02-12 12:52 GMT+09:00 Craig Ringer < > >> craig@ > >> >: >>> Hi all >>> >>> I've just seen another case of data loss due to misuse of / >>

Re: [DOCS] PATCH: Warn users about tablespace abuse data loss risk

2014-02-12 12:52 GMT+09:00 Craig Ringer : > Hi all > > I've just seen another case of data loss due to misuse of / > misunderstanding of tablespaces: > > http://dba.stackexchange.com/questions/58704/how-do-i-access-a-old-saved-tablespace-after-reinstalling-postgres > > and it's prompted me to write

[DOCS] 9.3: mention checksum feature in "29.1. Reliability"

This page: http://www.postgresql.org/docs/9.3/static/wal-reliability.html says: "Data pages are not currently checksummed, though full page images recorded in WAL records will be protected. Data pages have a 16-bit field available for future use with a data page checksum feature." Patch with

[DOCS] Update for sample PL/PgSQL function (section 40.6.4)

In the PL/PgSQL documentation, section "40.6.4. Looping Through Query Results" [1] contains a sample function which refreshes pseudo-materialized views. As 9.3 has proper materialized views, I thought it could do with updating. There was also an erroneous "%s" in a RAISE NOTICE, and I've tweaked th

Re: [DOCS] Correction for: "21.6. Tablespaces"

2013/7/31 Fujii Masao : > On Wed, Jul 31, 2013 at 1:49 PM, Ian Lawrence Barwick > wrote: >> Hi >> >> The last paragraph on the page "21.6. Tablespaces": >> >> "and after you restart the server, update the pg_tablespace catalog >> wi

[DOCS] Correction for: "21.6. Tablespaces"

Hi The last paragraph on the page "21.6. Tablespaces": "and after you restart the server, update the pg_tablespace catalog with the new locations" is partially inaccurate as of PostgreSQL 9.2, as the spclocation column which is meant here was removed in 9.2 [2]). Patch attached; I also added a

[DOCS] pgFouine -> pgBadger?

The "Log File Maintenance" section: http://www.postgresql.org/docs/current/static/logfile-maintenance.html mentions pgFouine, but that project doesn't seem to have been updated since 2010 and appears to have been superseded by the actively maintained pgBadger. Patch attached. Regards Ian Bar

[DOCS] The Parser Stage: "plain ASCII text" ?

"The parser has to check the query string (which arrives as plain ASCII text) for valid syntax." http://www.postgresql.org/docs/current/interactive/parser-stage.html#AEN87498 Surely this would be "plain text", not "plain ASCII text"? Ian Barwick -- Sent via pgsql-docs mailing list (pgsql-docs

Re: [DOCS] Underscorces in copy-documentation (9.0 and higher)

2013/3/20 Tom Lane : > Mario Duhanic writes: >> Hi, >>- http://www.postgresql.org/docs/9.2/static/sql-copy.html, >>- http://www.postgresql.org/docs/9.1/static/sql-copy.html and >>- http://www.postgresql.org/docs/9.0/static/sql-copy.html > >> have underscores ("_") where there should be

[DOCS] Small patch for "CREATE TRIGGER" documentation

I found this sentence somewhat confusing: "It is possible for a column's value to change even when the trigger is not fired," http://www.postgresql.org/docs/devel/static/sql-createtrigger.html#SQL-CREATETRIGGER-NOTES More precise would be something along the lines "It is possible that changes to

Re: [HACKERS] [DOCS] Contrib module "xml2" status

2013/2/22 Andrew Dunstan : > > On 02/21/2013 12:56 PM, Magnus Hagander wrote: >> >> On Thu, Feb 21, 2013 at 6:39 PM, Robert Haas >> wrote: >>> >>> On Wed, Feb 20, 2013 at 11:58 AM, Ian Lawrence Barwick >>> wrote: >>>> >>

[DOCS] Contrib module "xml2" status

Hi I'm not sure if this is a documentation or hackers issue, but the documentation page for contrib module "xml2" refers to PostgreSQL 8.4 in the future tense: "It is planned that this module will be removed in PostgreSQL 8.4 in favor of the newer standard API" http://www.postgresql.org/docs/

Re: [HACKERS] Re: Privileges for INFORMATION_SCHEMA.SCHEMATA (was Re: [DOCS] Small clarification in "34.41. schemata")

rg/message-id/200612211146.kblbklqa001...@wwwmaster.postgresql.org [7] http://www.postgresql.org/message-id/50aff3fe.4030...@gmail.com [8] Not that I'm claiming MySQL's implementation is authoritative or anything Regards Ian Lawrence Barwick -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

[DOCS] Small clarification in "34.41. schemata"

is owned by the superuser. Does the documentation need clarifying? I'd suggest something like: The view schemata contains all schemas in the current database that are owned by a currently enabled role, or all schemas if the currently enabled role is a superuser. Regards Ian Lawrence Ba