Hello,
I'm developing my first patch for PostgreSQL. The target is v9.2.
I'm trying to build HTML docs on Windows Vista (32-bit) with the latest v9.1
Git branch, but the build fails. I followed the procedures in the v9.0
manual. Could you tell me what might be the cause? The situation is as
f
From: "Robert Haas"
2011/5/15 MauMau :
Hello,
I'm developing my first patch for PostgreSQL. The target is v9.2.
I'm trying to build HTML docs on Windows Vista (32-bit) with the latest
v9.1
Git branch, but the build fails. I followed the procedures in the v9.0
manual. Co
w_page()? Having a quick look at the code, it seems
that the function can also handle indexes.
table and returns a copy as a bytea value. This allows a
Regards
MauMau
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
From: "Vik Fearing"
On 08/10/2014 03:24 PM, MauMau wrote:
Could you also improve the doc by changing "table" to "relation" in the
description of get_raw_page()? Having a quick look at the code, it
seems that the function can also handle indexes.
table
t's located in src/common/relpath.c.
However, I did find another occurence in the documentation, so third
patch attached.
You are right, I was looking at the code of 9.3.4 at hand. The latest code
certainly has the accurate HINT message.
Your v3 patch looks reasonable.
Regards
MauMau
--
Se
ause it is not flushed to
disk.The patch consists of a program called pg_copy which can be used
instead of cp/copy, and a doc fix to suggest using mv. I made it following
the favorable suggestions from people.
Regards
MauMau
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.or
From: "Josh Berkus"
Yah? Does it work on Windows?
Yes. pg_copy is meant to be a replacement for cp/copy, not for the entire
archive_command script. It just opens, reads, writes, syncs, and closes the
file.
Regards
MauMau
--
Sent via pgsql-docs mailing list (pgsql-docs@post
#x27;s buffer -> OS cache ->
disk
For reference, \copy of psql is described like this:
Tip: This operation is not as efficient as the SQL COPY command because all
data must pass through the client/server connection. For large amounts of
data the SQL command might be preferable.
