Re: [DOCS] Docs patch for REFRESH MATERIALIZED VIEW lock level

On 2 November 2015 at 21:05, Kevin Grittner wrote: > On Sunday, November 1, 2015 7:59 PM, Craig Ringer > wrote: > >> The explicit locking docs mention the lock taken by REFRESH >> MATERIALIZED VIEW CONCURRENTLY, but not plain REFRESH MATERIALIZED >> VIEW. Pa

[DOCS] Docs patch for REFRESH MATERIALIZED VIEW lock level

The explicit locking docs mention the lock taken by REFRESH MATERIALIZED VIEW CONCURRENTLY, but not plain REFRESH MATERIALIZED VIEW. Patch. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services

[DOCS] [PATCH] Advise devs to prefer server_version_num over parsing the version

We've had server_version_num since 8.2. This patch advises devs to prefer to use it instead of parsing version() or server_version unless using libpq, in which case PQserverVersion should be used. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development,

Re: [DOCS] xref labels: "Chapter 33", "Section 33.2"

On 17 February 2015 at 15:27, Tom Lane wrote: > Bruce Momjian writes: > > On Mon, Feb 16, 2015 at 05:05:39PM +1300, Craig Ringer wrote: > >> I can't seem to make an render the > ... > >> element text. The DocBook documentation implies that this should be

[DOCS] bgworker / SPI docs patches

tever) everywhere in the docs. I'd like to progressively add them to every section, refentry, chapter, etc that has an id. I hope this is useful. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services From c73d1303cb3474c

[DOCS] xref labels: "Chapter 33", "Section 33.2"

Am I just missing something obvious? Is this linking style, where the chapter title is ignored, by design? I can just use elements, but I'd really rather avoid endlessly repeating things like Server Programming Interface (SPI) everywhere, especially as that's the whole purpose

[DOCS] [PATCH] Advise devs to prefer server_version_num over parsing the version

We've had server_version_num since 8.2. Advise devs to prefer to use it instead of parsing version() or server_version . -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services From db8b82c54e492312c3dc6d9081790753389

Re: [JDBC] [DOCS] JDBC documentation - issue report

;m reluctant to remove this until Java SE 5 is dead and gone and PgJDBC drops JDBC4 support. Sometime around 2030 at the rate adoption of newer releases is going. A note to say that explicit loading is ineffective if using a JDBC4 driver and on Java 1.6 or newer would be reasonable. -- Craig Ringer

[DOCS] PQping docs note

uld apply cleanly to master with "git am". -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services >From 4ba9bca8a7cf6b72a9fae6b4ee8abb54d9ad8d8a Mon Sep 17 00:00:00 2001 From: Craig Ringer Date: Thu, 26 Jun 2014 1

[DOCS] archive_command vs recovery_command paths

hat better explain that we assume there's shared storage like NFS involved, and if there isn't you need to use commands like scp/rsync instead, or use tools like WAL-E. I'm not going to get time to do this one for at least a few days, but I'm posting it now partly so I don't

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

and tweaking the example. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services >From a754f61f5228e0d066edc10ae903282b36f9a256 Mon Sep 17 00:00:00 2001 From: Craig Ringer Date: Wed, 12 Feb 2014 11:48:23 +0800 Subject: [PATCH]

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

imply copying the table into a different MySQL install's data directory. It doesn't even have to be the same version! Users are clearly surprised that PostgreSQL tablespaces don't have the same properties. Thoughts? -- Craig Ringer http://www.2ndQuadrant.com/ Po

Re: [DOCS] [HACKERS] Documentation epub format

he main thing that needs is a better ebook standard with pre-built machine-readable keyword indexes, IMO. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.o