On Fri, Oct 14, 2011 at 1:17 AM, Fujii Masao wrote:
>> Slightly updated patch attached.
>
> Looks good.
Committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your
On Thu, Oct 13, 2011 at 10:44 AM, Josh Kupershmidt wrote:
> On Wed, Oct 12, 2011 at 1:14 AM, Fujii Masao wrote:
>> I'm not sure if there are other use cases during normal operation.
>
> If there's no real use-case for the command, I think the existing text
> of "not intended for use during normal
On Wed, Oct 12, 2011 at 1:14 AM, Fujii Masao wrote:
> On Wed, Oct 12, 2011 at 12:02 PM, Josh Kupershmidt wrote:
> It's for preventing pg_start_backup() from taking lots of time? If so,
> you're right in 8.3 and before. In 8.4 and later, instead, you can specify
> whether pg_start_backup() perfor
On Wed, Oct 12, 2011 at 12:02 PM, Josh Kupershmidt wrote:
> Basically, I think the page should be structured to emphasize
> 1.) what is a "checkpoint" to a user who is not familiar with the term, and
> 2.) why would a user want to use the CHECKPOINT command?
>
> To tackle 1.), I think a little b
Hi all,
I think that the page about the CHECKPOINT command:
http://www.postgresql.org/docs/current/static/sql-checkpoint.html
could really use some work.
The page is quite obtuse if you don't already understand what a checkpoint is.
The first sentence goes:
| Write-Ahead Logging (WAL) puts a
