. Thought?
Regards,
--
Fujii Masao
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
e parameter of the same name"
>> https://www.postgresql.org/docs/9.6/static/runtime-config-resource.html
>> (effective_io_concurrency)
>
> Good catch, that's clearly missing.
Pushed. Thanks!
Regards,
--
Fujii Masao
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
ence, this:
>
> "it must constructed so that each process which executes the plan"
>
> should be:
>
> "it must be constructed so that each process which executes the
> plan".
>
> That is, the "be" is missing.
Fixed. Thanks for the repo
On Wed, Jul 20, 2016 at 6:17 PM, Alexander Law wrote:
> Hello,
> It seems that the udt_privileges view' description contains an incorrect
> copy-pasted word. Fix attached.
Pushed. Thanks!
Regards,
--
Fujii Masao
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresq
On Sat, Dec 5, 2015 at 12:56 AM, Alvaro Herrera
wrote:
> Fujii Masao wrote:
>
>> Sorry for not reviewing the patch before you push it...
>>
>> In HEAD, I ran very simple test case:
>>
>> 1. enable track_commit_timestamp
>> 2. start the server
On Tue, Nov 17, 2015 at 6:43 AM, Alvaro Herrera
wrote:
> I paraphrase Fujii Masao, who wrote:
>
>> 1. Start the master and standby servers with track_commit_timestamp enabled.
>> 2. Disable track_commit_timestamp in the master and restart the master
>> server.
>> 3
differently
in #2, #5, and #7 though the settings of track_commit_timestamp are same
in both servers, i.e., it's disabled in the master but enabled in the standby.
I was thinking that whether committs is active or not should depend on
the setting of track_commit_timestamp *after* the prom
On Fri, Oct 2, 2015 at 11:58 PM, Alvaro Herrera
wrote:
> Fujii Masao wrote:
>
>> What happens if pg_xact_commit_timestamp() is called in standby after
>> track_commit_timestamp is disabled in master, DeactivateCommitTs() is
>> called and all commit_ts files are removed
On Fri, Oct 2, 2015 at 3:12 AM, Alvaro Herrera wrote:
> Fujii Masao wrote:
>
>> I've not read the patch yet, but the patched server with
>> track_commit_timestamp
>> enabled caused the following PANIC error when I ran pgbench.
>
> Ah, that was a stupid typo: I
ml
> +++ b/doc/src/sgml/storage.sgml
> @@ -990,7 +990,7 @@ data. Empty in ordinary tables.
>
>
> All the details can be found in
> - src/include/access/htup.h.
> + src/include/access/htup_details.h.
>
>
> Patch is attached.
Applied. Thanks!
Regards,
--
Fu
pgbench.
PANIC: could not access status of transaction 2457
DETAIL: Could not read from file "pg_commit_ts/" at offset 24576: Success.
STATEMENT: END;
The procedure to reproduce the PANIC error is,
1. Enable track_commit_timestamp
2. Start up the server
3. Run pgbench -i -s10
4.
On Thu, Sep 10, 2015 at 3:05 PM, Michael Paquier
wrote:
> On Thu, Sep 10, 2015 at 12:42 AM, Fujii Masao wrote:
>> On Tue, Jul 21, 2015 at 9:59 AM, Michael Paquier
>> wrote:
>>> On Tue, Jul 21, 2015 at 6:54 AM, Vignesh Raghunathan
>>> wrote:
>>>&
documentation is mistaken. The two bytes of pd_tli have been
> switched to pd_checksum in 9.3, hence only the first field is relevant
> for WAL, aka pd_lsn. Looking at this portion of the docs I think that
> it should be updated as attached, mentioning pd_checksum as well.
Also the type of pd
On Thu, Jul 16, 2015 at 1:07 PM, Fujii Masao wrote:
> On Wed, Jul 15, 2015 at 5:57 PM, Alvaro Herrera
> wrote:
>> Fujii Masao wrote:
>>> Hi,
>>>
>>> "25.5.3. Administrator's Overview" in the document
>>>
then.
>
> There's no existing precedent for a feature that lets the standby be
> different from the master *in any way*. So I don't see why we should
> start here. I think the reasonable definition is that the GUC
> controls whether the master tries to update the SLRU (and
On Wed, Jul 15, 2015 at 5:57 PM, Alvaro Herrera
wrote:
> Fujii Masao wrote:
>> Hi,
>>
>> "25.5.3. Administrator's Overview" in the document
>> -
>> The setting of some parameters on the standb
ed_transactions
max_locks_per_transaction
-
I found that the value of max_worker_processes on the standby also
must be equal to or greater than the value on the master. So we should
just add max_worker_processes to this paragraph. Patch attached.
Regards,
--
Fujii Masa
On Fri, Jun 12, 2015 at 1:47 AM, Fujii Masao wrote:
> Hi,
>
> System catalogs and views should be listed in alphabetical order,
> but only pg_file_settings view not. The attached patch fixes this
> alphabetization.
>
> The patch also fixes two typos in comments relate
Hi,
System catalogs and views should be listed in alphabetical order,
but only pg_file_settings view not. The attached patch fixes this
alphabetization.
The patch also fixes two typos in comments related to pg_file_settings.
Regards,
--
Fujii Masao
*** a/doc/src/sgml/catalogs.sgml
--- b/doc
On Thu, Jun 4, 2015 at 3:22 AM, Alvaro Herrera wrote:
> Fujii Masao wrote:
>> Hi,
>>
>> The descriptions of pg_class.relminmxid and pg_database.datminmxid
>> have some minor problems in the doc. Seems the attached patch needs
>> to be applied.
>
> Looks r
Hi,
The descriptions of pg_class.relminmxid and pg_database.datminmxid
have some minor problems in the doc. Seems the attached patch needs
to be applied.
Regards,
--
Fujii Masao
*** a/doc/src/sgml/catalogs.sgml
--- b/doc/src/sgml/catalogs.sgml
***
*** 2018,2025
All
gt; for Committer"
>
>
> This last patch is good. I it good fix of this problem - and usage of
> qualified identifiers is common and recommended solution.
>
> It is really ready for commiter.
Applied. Thanks!
Regards,
--
Fujii Masao
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
9.3.4 at hand. The latest code
> certainly has the accurate HINT message.
>
> Your v3 patch looks reasonable.
Thanks for the patch! Applied.
Regards,
--
Fujii Masao
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
xed the HINT message
"HINT: Valid fork names are "main", "fsm", and "vm".",
so that the initialization fork is included in that message.
This also needs to be back-patched to those versions.
Regards,
--
Fujii Masao
--
Sent via pgsql-docs mailing list
row)
postgres=# SET tcp_keepalives_idle TO '1024ms';
SET
postgres=# SHOW tcp_keepalives_idle ;
tcp_keepalives_idle
-
1
(1 row)
Regards,
--
Fujii Masao
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Sun, May 11, 2014 at 12:39 PM, Amit Langote wrote:
> Hi,
>
> Attached fixes a minor typo on test_shm_mq doc page
>
> s/"has been send"/"has been sent"
Applied. Thanks!
Regards,
--
Fujii Masao
--
Sent via pgsql-docs mailing list (pgsql-docs@post
specified, streaming starts on
> timeline tli; otherwise, the server's current timeline is selected.". Looks
> like the 9.3 docs always require a timeline to be specified.
ISTM that TIMELINE is optional both in HEAD and 9.3. So I fixed the document
in both versions. Thanks for the rep
When the standby
successfully reconnects to the master, lots of WAL files would
be streamed and they might already have WAL entries that
conflict with standby queries. No?
Regards,
--
Fujii Masao
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
ngs. Patch attached.
Regards,
--
Fujii Masao
*** a/doc/src/sgml/recovery-config.sgml
--- b/doc/src/sgml/recovery-config.sgml
***
*** 142,197 restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
-
-
On Wed, Nov 27, 2013 at 11:34 AM, Josh Kupershmidt wrote:
> Hi,
> It looks like a duplicated '>' character snuck into the 9.1.10 release
> notes, fix attached.
Thanks! Committed.
Regards,
--
Fujii Masao
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
T
ate as of PostgreSQL 9.2, as the spclocation
> column which is meant
> here was removed in 9.2 [2]).
>
> Patch attached;
Thanks! Committed.
> I also added a link to the "pg_tablespace" page.
I used instead of because xreflabel of catalog-pg-tablespace
is not defined.
Regards
the input directory
of pg_dump is not true. If the target directory is empty, pg_dump
can continue its process even if the directory exists.
> In this case the directory is created by pg_dump and must not exist before.
The attached patch fixes these wrong descriptions.
Regards,
--
Fujii
On Wed, Oct 24, 2012 at 11:54 PM, Fujii Masao wrote:
> Hi,
>
> I found the old information about -l option of pg_resetxlog in its document.
>
>> pg_resetxlog [-f] [-n] [-o oid] [-x xid] [-e xid_epoch] [-m mxid] [-O mxoff]
>> [-l timelineid,fileid,seg] datadir
>
&
;timelineid,fileid,seg' part should be changed to 'xlogfile'. Patch attached.
I chose the term 'xlogfile' here because it's used in help message of
pg_resetxlog.
Regards,
--
Fujii Masao
pg_resetxlog_doc_v1.patch
Description: Binary data
--
Sent via pgsql-docs mailing
.
Regards,
--
Fujii Masao
tablespace_option_v1.patch
Description: Binary data
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Fri, Mar 23, 2012 at 11:12 AM, Robert Haas wrote:
> On Thu, Mar 22, 2012 at 9:21 PM, Fujii Masao wrote:
>> On Fri, Mar 23, 2012 at 4:41 AM, Robert Haas wrote:
>>> Update docs on numeric storage requirements.
>>>
>>> Since 9.1, the minimum overhead is thr
On Fri, Mar 23, 2012 at 4:41 AM, Robert Haas wrote:
> Update docs on numeric storage requirements.
>
> Since 9.1, the minimum overhead is three bytes, not five.
Thanks for the commit!
I think that it's worth backporting this to 9.1. Thought?
Regards,
--
Fujii Masao
NIPPON
xes this.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 58e46b5..91dc35d 100644
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -568,7 +568,7 @@ NUMERIC
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
helpful to link to that. What a "restartpoint" is explained in also
http://www.postgresql.org/docs/current/static/wal-configuration.html
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Hi,
It's helpful to add pg_resetxlog into the index in the document.
Patch attached.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
pg_resetxlog_index_v1.patch
Description: Binary data
--
Sent via pgsql-docs mailing list (pgsql
On Wed, Sep 21, 2011 at 2:02 PM, Magnus Hagander wrote:
> On Wed, Sep 21, 2011 at 03:58, Fujii Masao wrote:
>> On Tue, Sep 20, 2011 at 10:34 PM, Magnus Hagander
>> wrote:
>>> On Tue, Sep 20, 2011 at 15:17, Peter Eisentraut wrote:
>>>> At
>>>&g
;> ought to contain at least %p, right?
>
> Should always need both %p and %f, no?
Yes unless the script extracts the file name from the path given as %p.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
ameter,
"SUPERUSER" should be changed to "REPLICATION"? The
attached patch does s/"SUPERUSER"/"REPLICATION".
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
diff --git a/doc/src/sgml/recovery-config.sgml b/d
Hi,
Bruce lowercased the replication status in pg_stat_replication before.
But the status in the document are still in uppercase. We should lowercase
them, too. Patch attached.
http://archives.postgresql.org/pgsql-committers/2011-04/msg00342.php
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND
Hi,
recovery.conf is not listed in the index, though postgresql.conf and
pg_hba.conf are. Which sometimes annoys me when I search
recovery.conf page from the index. What about applying the attached
patch which marks "recovery.conf" as an index term?
Regards,
--
Fujii Masao
NIPPON TEL
ned
Attached patch fixes the problem.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
*** a/doc/src/sgml/ddl.sgml
--- b/doc/src/sgml/ddl.sgml
***
*** 3021,3027 ANALYZE measurement;
foreign data wrapper. A foreig
command line.
-
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
*** a/doc/src/sgml/config.sgml
--- b/doc/src/sgml/config.sgml
***
*** 2107,2112 SET ENABLE_SEQSCAN TO OFF;
--- 2107,2116
parameter to
On Tue, Jun 7, 2011 at 1:56 AM, Tom Lane wrote:
> Fujii Masao writes:
>> http://developer.postgresql.org/pgdocs/postgres/auth-pg-hba-conf.html
>>> An IP address is specified in standard dotted decimal notation with
>>> a CIDR mask length. The mask length indicates t
d patch just removes that statement.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
*** a/doc/src/sgml/client-auth.sgml
--- b/doc/src/sgml/client-auth.sgml
***
*** 231,238 hostnossl database user
An IP address is
command line.
for them? The former is used also for other PGC_BACKEND
parameters (e.g., post_auth_delay). I attached the patch.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
*** a/doc/src/sgml/config.sgml
--- b/doc/src/sgml/config.sgml
.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
pg_ctl_kill_doc.patch
Description: Binary data
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Hi,
We seem to have forgotten to add the reference to DEFAULT clause
into the following syntax in alter-table.sgml. How about the attached
patch?
ADD [ COLUMN ] column type [ column_constraint [ ... ] ]
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source
m just going to remove the whole paragraph.
Fair enough.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
t other misconfigurations can be still harm, so I thought
the sentence still needs to be in the document.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subsc
ct because of wrong configuration (e.g., name of host to
connect to). For additional connection variables, see Section 31.13.
-
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
(e.g., password authentication).
> For additional connection variables, see Section 31.13, and for
> passwords, also see Section 31.14.
The above also seems to be obsolete, thanks to recently-introduced
PQping. Can we remove that?
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE
On Fri, Oct 15, 2010 at 6:19 PM, Simon Riggs wrote:
> On Thu, 2010-10-14 at 12:00 +0900, Fujii Masao wrote:
>>
>> 29.4. WAL Configuration
>>
>> There will always be at least one WAL segment file, and will normally not
>> be more than
correct is
(2 + checkpoint_completion_target) * checkpoint_segments +
wal_keep_segments + 1
The attached patch fixes this fault.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
num_of_wal_formula_v2.patch
Description: Binary data
the
> suggestions on-list first, before getting too invested. So, please
> comment if you have an opinion on this.
Agreed.
And, ISTM that we should mention that we must not just specify
pg_archivecleanup in archive_cleanup_command when there are multiple
standby servers. This is because, in t
hivecleanup -d ../archive %r 2>>cleanup.log'
This is not a typo. Triple dots ... is used as replaceable part of the path,
and is used also elsewhere. Though I agree that's somewhat confusing.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Softwar
Hi,
The release note says "Allow continuous archive (WAL) files
to be streamed to a standby system" about SR. But no archive
files are streamed in SR. So we should get rid of the word
"archive" from that sentence? Here is the patch.
Regards,
--
Fujii Masao
NIPPON TEL
ecord-based log shipping using this
alternative method, though this requires custom development, and changes
-will still only becomes visible to hot standby queries after a full WAL
+will still only become visible to hot standby queries after a full WAL
file has been shipped.
Reg
Hi,
pgupgrade.sgml still uses 8.5 rather than 9.0 in
some places. I attached the patch to s/"8.5"/"9.0".
And it fixes another typo in pgupgrade.sgml.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
typo_pgupgrade_sgml_
>> specific than "Notes", perhaps "NOTIFY Notes". Is there a way to
>> control the label used for an index link?
>
> Doesn't look like there is :-(
How about creating new subsection "pg_notify" under "Notes" and placing
the description
Hi,
In the index of current document, "pg_notify" is tied to the
word "Notes". This is odd for me.
http://developer.postgresql.org/pgdocs/postgres/bookindex.html
How about the patch to tie "pg_notify" to "NOTIFY"?
Regards,
--
Fujii Masao
NIPPON TELE
On Wed, Apr 28, 2010 at 3:19 PM, Heikki Linnakangas
wrote:
> Fujii Masao wrote:
>> On Wed, Apr 28, 2010 at 4:52 AM, Heikki Linnakangas
>> wrote:
>>> Fujii Masao wrote:
>>>> While the server configuration parameters are listed in
>>>> the
On Wed, Apr 28, 2010 at 4:52 AM, Heikki Linnakangas
wrote:
> Fujii Masao wrote:
>> While the server configuration parameters are listed in
>> the index page, why not the recovery ones? It's very
>> inconvenient to be unable to reach the document of them
>> immedia
page?
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
tions will be accepted only
> for superusers, and no new replication connections will be accepted.
>
> I think that's pretty simple and clear.
Yeah, I'm sold.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pg
privilege from replication connection
3. Your proposal
Treat superuser replication connection like non-superuser one
Since 3. is confusing for me, I like 1. or 2.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
d like to forbid
replication connection to use the slots, I think that we should
just get rid of a superuser privilege from it instead.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
, e.g. /bin/true, effectively disables
archiving, but also breaks the chain of WAL files needed for
archive recovery, so it should only be used in unusual circumstances.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent
x_connections + autovacuum_max_workers + max_wal_senders + 1
--
This change looks like minor adjustments rather than major changes.
I have one question:
In the patch, max_wal_senders is ignored by CheckRequiredParameterValues()
as autovacuum_max_workers is already. Is this OK for HS?
Regards,
On Thu, Apr 1, 2010 at 11:00 AM, Robert Haas wrote:
> On Wed, Mar 31, 2010 at 9:58 PM, Fujii Masao wrote:
>> On Thu, Apr 1, 2010 at 10:52 AM, Robert Haas wrote:
>>> On Wed, Mar 31, 2010 at 9:50 PM, Fujii Masao wrote:
>>>>> That's an interesting point
On Thu, Apr 1, 2010 at 10:52 AM, Robert Haas wrote:
> On Wed, Mar 31, 2010 at 9:50 PM, Fujii Masao wrote:
>>> That's an interesting point, do streaming replication connections
>>> consume superuser_reserved_connections slots?
>>
>> Yes. Since SR conne
On Thu, Apr 1, 2010 at 5:39 AM, Heikki Linnakangas
wrote:
> Fujii Masao wrote:
>> ***
>> *** 829,834 if (!triggered)
>> --- 826,834
>>
>> Set the maximum number of concurrent connections from the standby
>>
-logging.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
doc_skip_logging_v1.patch
Description: Binary data
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
failure on the primary.
* Clarify how to safely take an incrementally updated backups.
* Define the recovery.conf parameters as an index term.
* Describe how to use recovery.conf.
Any comments are welcome.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source
On Thu, Mar 4, 2010 at 9:00 PM, Fujii Masao wrote:
>> And, when we start an archive recovery from the backup from the standby,
>> we seem to reach a safe starting point before database has actually become
>> consistent. It's because backupStartLoc is zero. Isn't t
teger" rather than
"int". In the description of other parameters, "integer" has been
used. Here is the patch.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
ssl_renegotiation_limit_type_v1.patch
Description: Binary d
conf parsing smarter, if
> only for consistency with postgresql.conf, or merge them completely...
+10
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes
ped with a backslash,
i.e., \' and \\.
---
So I'd like to copy and paste the description about conninfo except the
above. Thought? Here is the patch.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
*** a/doc/src/sgml/recovery-
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
> looking for libpq info, rather than providing more generic information
> which may be better placed in an appendix or something similar.
Since conninfo is tied closely to libpq, its information should
be in libpq chapter rather than an appendix or another chapter. No?
Regards,
--
Fujii Ma
On Thu, Feb 4, 2010 at 4:28 PM, Fujii Masao wrote:
> Sorry for resurrecting an old argument.
> http://archives.postgresql.org/message-id/200812051441.mb5efg1m007...@wwwmaster.postgresql.org
>
> I got the complaint about this behavior of the current pg_stop_backup()
> in this mor
in the value must be escaped with a backslash,
i.e., \' and \\.
The currently recognized parameter key words are the same as above.
---
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-docs mailing list (pgsql-d
87 matches
Mail list logo
