> Another point: test_decoding does not have descriptions for their options
> neither.
> Should we also add as well?
Yes, I think it's worth doing this (but it's better to do as a separate patch).
TBH this was already on my TODO list.
Regards,
--
Fujii Masao
On Wed, Aug 13, 2025 at 11:23 PM Robert Treat wrote:
> it but okay... but the true value add for me was adding the index
> entry for the source repository information, so I'd like to see that
> added either way.
+1 to add the index entry.
Regards,
--
Fujii Masao
nclude the full term "Grand Unified Configuration" here, e.g.,
"Grand unified configuration (GUC)", similar to how "Log sequence number (LSN)"
is shown in the glossary? Even though it's already in the acronyms docs,
it might be helpful to include it in the glossary as well.
Regards,
--
Fujii Masao
ut I don’t have a strong opinion. If we decide to do it, it would
be better to make the change in a separate patch.
Regards,
--
Fujii Masao
On Wed, Aug 6, 2025 at 8:36 PM Peter Eisentraut wrote:
>
> On 03.08.25 03:32, Fujii Masao wrote:
> > The current documentation for pgoutput is buried in the logical streaming
> > replication protocol section (in protocol.sgml), and there's no index entry
> > for it. T
to locate this information myself, so I'd like to
propose moving the pgoutput documentation to the logical decoding section
and adding an index entry. The attached patch does that. I think this change
will make it much easier for users to find the relevant details.
Thoughts?
Regards,
--
F
On Tue, Jul 22, 2025 at 2:10 PM Michael Paquier wrote:
>
> On Thu, Jul 03, 2025 at 01:30:13AM +0900, Fujii Masao wrote:
> > BTW, all current index entries point to the top of the pg_buffercache
> > docs. Would it be better if each entry pointed directly to its relevant
> &
On 2025/07/18 16:15, Shinya Kato wrote:
On Fri, Jul 18, 2025 at 12:33 PM Fujii Masao
wrote:
On 2025/07/18 11:35, Shinya Kato wrote:
On Thu, Jul 10, 2025 at 4:48 PM Fujii Masao wrote:
Hi,
pg_recvlogical continuously writes to the file specified with the --file option,
which means the
On 2025/07/18 11:35, Shinya Kato wrote:
On Thu, Jul 10, 2025 at 4:48 PM Fujii Masao wrote:
Hi,
pg_recvlogical continuously writes to the file specified with the --file option,
which means the output file can grow indefinitely. To manage file size,
some users may want to rotate the output
l.org/gitweb/?p=postgresql.git;a=commitdiff;h=f6ffbeda00e08c4c8ac8cf72173f84157491bfde
--
Fujii Masao
NTT DATA Japan Corporation
On 2025/07/15 23:27, Robert Treat wrote:
On Tue, Jul 15, 2025 at 1:44 AM Laurenz Albe wrote:
On Tue, 2025-07-15 at 01:51 +0900, Fujii Masao wrote:
On 2025/06/18 6:53, Robert Treat wrote:
I think the more cases where you document this behavior (and I do like
the idea of documenting it
that both
total_vacuum_time and n_ins_since_vacuum exclude VACUUM FULL.
Unless there are any objections, I'll commit this to master and
back-patch it to v18 only.
Regards,
--
Fujii Masao
NTT DATA Japan Corporation
From b1e64ee62915b883369a46e6add417acde15da88 Mon Sep 17 00:00:00 2001
From: Fujii Masao
On 2025/07/12 7:18, Daniel Gustafsson wrote:
On 11 Jul 2025, at 01:36, Fujii Masao wrote:
Since the prcp column isn't specified, its value is NULL. So shouldn't
the fourth field in the data line above be \N instead of 0.0?
It should, fixed in v3.
LGTM. Thanks!
Regards,
On 2025/07/11 7:22, Daniel Gustafsson wrote:
On 5 Jul 2025, at 19:29, Tom Lane wrote:
Fujii Masao writes:
On 2020/01/28 19:18, Daniel Gustafsson wrote:
This is only mentioned as an example of another input method, with a link to
the COPY page for more information. That being said, it&#
it's currently undocumented. So I'd like to
apply the attached patch that adds this information to the documentation.
Thought?
Regards,
--
Fujii Masao
NTT DATA Japan Corporation
From 3d0b0df5d21b570bbda75353c9ba230d0907e253 Mon Sep 17 00:00:00 2001
From: Fujii Masao
Date: Thu, 10 Jul
3 57 0 1994-11-29
Hayward 37 54 \N 1994-11-29
Regards,
[1]
https://postgr.es/m/175166227769.3157504.1136715805440673...@wrigleys.postgresql.org
--
Fujii Masao
NTT DATA Japan Corporation
On 2025/07/02 16:12, Fujii Masao wrote:
On 2025/07/01 13:52, Nisha Moond wrote:
On Mon, Jun 30, 2025 at 6:12 PM Fujii Masao wrote:
Is this true starting from v16, when logical replication from standby was
introduced?
In other words, in v15 and earlier, only max_slot_wal_keep_size could
ibute like this?
-
+
pg_buffercache_summary
Thought?
Regards,
--
Fujii Masao
NTT DATA Japan Corporation
From 06013d1d1fbaa64aa99f5067b2608ab833a92b3d Mon Sep 17 00:00:00 2001
From: Fujii Masao
Date: Thu, 3 Jul 2025 00:35:44 +0900
Subject: [PATCH v1] doc: Add missing index entries and
On 2025/07/01 13:52, Nisha Moond wrote:
On Mon, Jun 30, 2025 at 6:12 PM Fujii Masao wrote:
Is this true starting from v16, when logical replication from standby was
introduced?
In other words, in v15 and earlier, only max_slot_wal_keep_size could cause
the wal_status to become "unres
On 2025/06/30 20:32, Nisha Moond wrote:
On Fri, Jun 27, 2025 at 5:40 PM Fujii Masao wrote:
On 2025/06/27 15:32, Nisha Moond wrote:
On Thu, Jun 26, 2025 at 1:33 PM Fujii Masao wrote:
On 2025/06/26 15:46, Nisha Moond wrote:
On Wed, Jun 25, 2025 at 9:56 PM Fujii Masao wrote:
Hi
On 2025/06/27 15:32, Nisha Moond wrote:
On Thu, Jun 26, 2025 at 1:33 PM Fujii Masao wrote:
On 2025/06/26 15:46, Nisha Moond wrote:
On Wed, Jun 25, 2025 at 9:56 PM Fujii Masao wrote:
Hi,
The pg_replication_slots documentation mentions only max_slot_wal_keep_size
as a condition under
On 2025/06/26 15:46, Nisha Moond wrote:
On Wed, Jun 25, 2025 at 9:56 PM Fujii Masao wrote:
Hi,
The pg_replication_slots documentation mentions only max_slot_wal_keep_size
as a condition under which the wal_status column can show unreserved or lost.
However, since commit ac0e33136ab
t; but the required WALs have not been
dropped yet if the slot was invalidated due to the timeout. How about removing
the
first part:
```
lost means that this slot is no longer usable.
```
Agreed. Attached is the updated version of the patch.
Regards,
--
Fujii Masao
NTT DATA Japan Corpor
yet.
https://www.postgresql.org/docs/devel/view-pg-replication-slots.html
So, how about updating the documentation to also mention
idle_replication_slot_timeout as a factor that can cause wal_status to
become unreserved or lost? Patch attached.
Regards,
--
Fujii Masao
NTT DATA Japan Corporation
On 2025/06/25 0:28, Fujii Masao wrote:
On 2025/06/19 19:34, Fujii Masao wrote:
Hi,
I'd like to propose three minor documentation fixes related to parameters
introduced in v18. Since they align with new content in that version,
I'm thinking to apply them to v18. Thoughts?
On 2025/06/19 19:34, Fujii Masao wrote:
Hi,
I'd like to propose three minor documentation fixes related to parameters
introduced in v18. Since they align with new content in that version,
I'm thinking to apply them to v18. Thoughts?
0001:
For parameters that exist as both configu
On 2025/06/24 0:46, Fujii Masao wrote:
On 2025/06/23 23:52, Daniel Gustafsson wrote:
On 23 Jun 2025, at 16:40, Fujii Masao wrote:
So barring any objections, I will commit the patch.
+1, LGTM.
Thanks for the review!
There is one more occurrence though, the relnotes seem to need
On 2025/06/23 23:52, Daniel Gustafsson wrote:
On 23 Jun 2025, at 16:40, Fujii Masao wrote:
So barring any objections, I will commit the patch.
+1, LGTM.
Thanks for the review!
There is one more occurrence though, the relnotes seem to need the
same treatment as they talk about UUID
On 2025/06/21 9:55, Masahiko Sawada wrote:
On Fri, Jun 20, 2025 at 11:33 PM Fujii Masao
wrote:
Hi,
Both the UUID data type and UUID functions pages define an index entry
for "UUID" that points to the data type section. As a result, the index
includes two identical entries link
ct section. The attached patch
updates this accordingly.
Thoughts?
Regards,
--
Fujii Masao
NTT DATA Japan Corporation
From e4fbb1929ccb43ff3adc282893167a2df6cbc1d2 Mon Sep 17 00:00:00 2001
From: Fujii Masao
Date: Fri, 20 Jun 2025 22:54:52 +0900
Subject: [PATCH v1] doc: Fix incorrect UUID index en
is "integer". This patch updates it
for consistency with other GUC parameter descriptions.
Regards,
--
Fujii Masao
NTT DATA Japan Corporation
From eee26a3c056e5c9951cc9c304c8a5b6ce4c44d9c Mon Sep 17 00:00:00 2001
From: Fujii Masao
Date: Thu, 19 Jun 2025 17:52:58 +0900
Subject: [PAT
On 2025/06/18 16:55, Fujii Masao wrote:
On 2025/06/18 15:50, Michael Paquier wrote:
On Wed, Jun 18, 2025 at 02:34:55PM +0900, Fujii Masao wrote:
Commit 302cf157592 added support for LIKE in CREATE FOREIGN TABLE.
In this feature, since indexes are not created for foreign tables,
comments
On 2025/06/19 4:50, Robert Treat wrote:
On Wed, Jun 18, 2025 at 3:55 AM Fujii Masao wrote:
Hi,
Commit 8492feb98f6 added support for parallel CREATE INDEX on GIN indexes.
However, there are still two places in the docs and two in the source code
comments that mention only B-tree and BRIN
On 2025/06/18 15:50, Michael Paquier wrote:
On Wed, Jun 18, 2025 at 02:34:55PM +0900, Fujii Masao wrote:
Commit 302cf157592 added support for LIKE in CREATE FOREIGN TABLE.
In this feature, since indexes are not created for foreign tables,
comments on indexes are not copied either.
Good
. Patch
attached.
Regards,
--
Fujii Masao
NTT DATA Japan Corporation
From 649b27e536194589c2bf85a05cb84e731dbfeac0 Mon Sep 17 00:00:00 2001
From: Fujii Masao
Date: Wed, 18 Jun 2025 16:30:36 +0900
Subject: [PATCH v1] doc: Mention GIN indexes support parallel builds.
Commit 8492feb98f6 added
ached.
Regards,
--
Fujii Masao
NTT DATA Japan Corporation
From e6a023b56f790c9995463d75e6101e5eaf49e98b Mon Sep 17 00:00:00 2001
From: Fujii Masao
Date: Wed, 18 Jun 2025 13:56:14 +0900
Subject: [PATCH v1] doc: Fix incorrect description of INCLUDING COMMENTS in
CREATE FOREIGN TABLE.
Commit 302cf157592
On 2025/06/18 1:34, Jelte Fennema-Nio wrote:
On Tue, 17 Jun 2025 at 18:32, Fujii Masao wrote:
Hi,
Commit 285613c60a7 added the min_protocol_version and max_protocol_version
connection options to libpq. However, their descriptions currently appear
in the middle of the unrelated
placement?
To make the documentation more intuitive and easier to navigate,
I suggest moving these entries after the SSL-related options.
Attached is a patch that does that.
Thanks,
--
Fujii Masao
NTT DATA Japan Corporation
From de4ba3e771840024f07b5132baddeeb1dd611709 Mon Sep 17 00:00:00 2001
From
umentation change to v13?
As for total_vacuum_time, since it's new in v18, I'd like to apply
the proposed change there.
Regards,
--
Fujii Masao
NTT DATA Japan Corporation
On 2025/06/07 0:13, Robert Treat wrote:
On Fri, Jun 6, 2025 at 9:57 AM David G. Johnston
wrote:
On Friday, June 6, 2025, Fujii Masao wrote:
Hi,
Since last_vacuum and vacuum_count in pg_stat_all_tables explicitly mention
that they don't include VACUUM FULL ("not counting VACUUM
On 2025/06/07 3:11, Robert Treat wrote:
On Thu, May 22, 2025 at 7:17 AM Fujii Masao wrote:
I noticed that the documentation is missing references to the database
object statistics manipulation functions such as pg_restore_relation_stats
in a few relevant places. For instance, the MAINTAIN
ds
+ (not counting VACUUM FULL).
(This includes the time spent sleeping due to cost-based delays.)
Regards,
--
Fujii Masao
NTT DATA Japan Corporation
On 2025/05/23 23:46, Fujii Masao wrote:
On 2025/05/23 19:52, Kevin K Biju wrote:
Hi Fuiji,
I wasn't aware that support for exporting snapshots goes as far back as v10.
The change looks good.
Thanks for the review!
I've prepared two patches: one for v15 and later, and anoth
objections, I'll go ahead and commit and back-patch the
patch
to all supported branches.
Regards,
--
Fujii Masao
NTT DATA Japan Corporation
From 97f85a60cef32a12a1232d3d5e161718728d872f Mon Sep 17 00:00:00 2001
From: Fujii Masao
Date: Fri, 23 May 2025 10:18:04 +0900
Subject: [PATCH v1] doc: F
- snapshot export may suppress it with the
NOEXPORT_SNAPSHOT
+ Applications that do not require
+ snapshot export may suppress it with the SNAPSHOT
'nothing'
option.
Regards,
[1]
https://www.postgresql.org/message-id/CAMsr+YFjxv0T8Yi1Q=3tvdgviu2bm+fb_-xubtfx
hough
they're covered. Likewise, the pg_class catalog section describes
what can update fields like reltuples, but omits these functions,
which also affect those fields.
So I'd like to propose adding these missing references to improve clarity.
Patch attached. Thought?
Regards,
--
Fujii
On 2025/04/24 23:30, Robert Treat wrote:
On Wed, Apr 23, 2025 at 2:54 AM Fujii Masao wrote:
Hi,
In config.sgml, the entries for max_replication_slots and
max_active_replication_origins include secondary index terms:
max_replication_slots configuration
parameter
in a
arate index entries. But commit 04ff636cbce
split them into distinct parameters.
Patch attached.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
From fada9d65dd5c177e43179bcd5cc2e57d36b5d831 Mon Sep 17 00:00:00 2001
From: Fujii
On 2024/12/13 9:12, Michael Paquier wrote:
On Fri, Dec 13, 2024 at 12:08:06AM +0900, Fujii Masao wrote:
Yes, that sounds like a good idea. I've updated the patch accordingly.
LGTM.
Pushed. Thanks!
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Develo
On 2024/12/11 9:18, Michael Paquier wrote:
On Fri, Oct 18, 2024 at 02:25:15AM +0900, Fujii Masao wrote:
The documentation in wal.sgml explains that old WAL files cannot be
removed or recycled until they are archived (when WAL archiving is used)
or replicated (when using replication slots
summarization is enabled. Attached patch adds that clarification to
the documentation. Thought?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
From 1339bbb4096df0182913c19a6277a105a2f5bee8 Mon Sep 17 00:00:00 2001
From
On 2023/04/21 2:14, Jelte Fennema wrote:
Ah, yeah it seems I forgot to document that one. LGTM
Pushed. Thanks!
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATIONFrom 7aaa813665ed159725998988431be15687b01494 Mon Sep 17 00:00:00 2001
From: Fujii Masao
Date: Fri, 21 Apr 2023 00:34:39 +0900
Subject: [PATCH v1] doc: Add documentation for PGLOADBALANCEHOSTS
the default) means no limit. To create such a role, use CREATE ROLE
name CONNECTION LIMIT connlimit
LOGIN.
"To create such a role" sounds odd to me in this context. Instead, how about something
like "Specify connection limit upon role creation with CREATE ROLE name CONNECTION LI
On 2022/07/20 18:07, Alvaro Herrera wrote:
Hello
On 2022-Jul-20, Fujii Masao wrote:
Attached is the updated version of the patch. It separates the list
for GUC flags from the table entry for pg_settings_get_flags() and
adds the table for it at the bottom of the existing function table.
I
On 2022/07/20 16:26, Michael Paquier wrote:
On Wed, Jul 20, 2022 at 01:51:36PM +0900, Fujii Masao wrote:
Attached is the updated version of the patch. It separates the list
for GUC flags from the table entry for pg_settings_get_flags() and
adds the table for it at the bottom of the existing
the existing function table.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATIONFrom db55800943ec0df13f91fe0315a965cc95689273 Mon Sep 17 00:00:00 2001
From: Fujii Masao
Date: Wed, 20 Jul 2022 13:30:58 +0900
Subject: [PATCH] docs
-1.5.8.32.19.2.2.25.1.1.1
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATIONFrom 735f4f095516ac7b1d4d838aeada3acffb4ae036 Mon Sep 17 00:00:00 2001
From: Fujii Masao
Date: Fri, 15 Jul 2022 22:19:58 +0900
Subject: [PATCH] Improve
On 2022/02/18 19:59, Peter Eisentraut wrote:
On 18.02.22 09:24, Fujii Masao wrote:
Or even backtrace should be logged by write_stderr() so that it's written to
eventlog if necessary? I just wonder why backtrace_symbols_fd() is used only in
ExceptionalCondition().
Probably because i
On 2022/02/18 16:07, Peter Eisentraut wrote:
On 07.02.22 17:42, Fujii Masao wrote:
On 2022/02/08 1:12, Peter Eisentraut wrote:
This change looks good to me. There is also backtrace code in assert.c that
might want the same treatment.
Yeah, that's good idea! The attached patch also
On 2022/02/08 1:12, Peter Eisentraut wrote:
This change looks good to me. There is also backtrace code in assert.c that
might want the same treatment.
Yeah, that's good idea! The attached patch also adds the same treatment into
assert.c.
Regards,
--
Fujii Masao
Advanced Comp
On 2022/02/04 9:48, Fujii Masao wrote:
On 2022/02/03 23:48, Tom Lane wrote:
Peter Eisentraut writes:
How about we issue a message when the backtrace is cut off. Then it's
immediately visible to the user, instead of hidden away somewhere in the
documentation. Something like
;nframes" useful enough to
include in the report?
Probably No because "nframes" is equal to "lengthof(buf)" in the case where
more than 100 frames are generated.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA
On 2022/02/02 16:20, Peter Eisentraut wrote:
On 01.02.22 18:04, Fujii Masao wrote:
The maximum number of backtrace frames logged by backtrace_functions is 100.
Isn't it better to document this information so that users can understand not
all backtrace always can be logged? Patch att
Hi,
The maximum number of backtrace frames logged by backtrace_functions is 100.
Isn't it better to document this information so that users can understand not
all backtrace always can be logged? Patch attached.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Researc
On 2022/01/08 1:41, Tom Lane wrote:
Fujii Masao writes:
In glossary, the title of each term about process seems to consist of the process name and
"(process)", e.g., Checkpointer (process). But I found that "(process)" is missing for
the following three terms about
to them.
- Auxiliary process
- Startup process
- WAL receiver
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATIONdiff --git a/doc/src/sgml/glossary.sgml b/doc/src/sgml/glossary.sgml
index 0c88988fa6..0fea6b4ab3 100644
--- a/do
On 2021/05/24 11:37, Masahiro Ikeda wrote:
Thanks for checking the patch!
I thought this patch will be applied in V15 dev cycle.
OK. I added the patch to the next CF.
https://commitfest.postgresql.org/33/3130/
I pushed the patch to 15dev. Thanks!
Regards,
--
Fujii Masao
Advanced
ch! Pushed.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
cs, "floating point" should be
used for the sake of consistenty, instead?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
On 2021/05/20 17:38, Masahiro Ikeda wrote:
On 2021/05/20 17:00, Fujii Masao wrote:
On 2021/05/20 9:46, Masahiro Ikeda wrote:
On 2021/05/18 20:10, Fujii Masao wrote:
pg_stat_database.tup_fetched:
Number of index entries returned by scans on indexes in this database
Is this the sum of
On 2021/05/20 9:46, Masahiro Ikeda wrote:
On 2021/05/18 20:10, Fujii Masao wrote:
On 2021/05/18 18:23, Masahiro Ikeda wrote:
On 2021/05/18 16:01, Fujii Masao wrote:
On 2021/05/18 13:20, Masahiro Ikeda wrote:
Tid Range Scan increments the tup_returned, and
On 2021/05/18 18:23, Masahiro Ikeda wrote:
On 2021/05/18 16:01, Fujii Masao wrote:
On 2021/05/18 13:20, Masahiro Ikeda wrote:
Tid Range Scan increments the tup_returned, and
pg_stat_all_tables.seq_tup_read is also incremented. I thought it's ok because
Tid Range Scan is like seque
On 2021/05/18 13:20, Masahiro Ikeda wrote:
On 2021/05/17 20:46, Fujii Masao wrote:
On 2021/05/17 18:58, Masahiro Ikeda wrote:
On 2021/05/17 15:32, Fujii Masao wrote:
On 2021/05/14 17:00, Masahiro Ikeda wrote:
Hi,
I worried the difference between "tup_returned" and &q
On 2021/05/17 18:58, Masahiro Ikeda wrote:
On 2021/05/17 15:32, Fujii Masao wrote:
On 2021/05/14 17:00, Masahiro Ikeda wrote:
Hi,
I worried the difference between "tup_returned" and "tup_fetched" in
pg_stat_database. I assumed that "tup_returned" m
index, tuples_returned is the number of index entries returned by
* the index AM, while tuples_fetched is the number of tuples successfully
* fetched by heap_fetch under the control of simple indexscans for this index.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research an
On 2021/04/16 10:20, Michael Paquier wrote:
On Thu, Apr 15, 2021 at 11:24:07PM +0900, Fujii Masao wrote:
I'm not sure why. But +1 to make them in alphabetical order.
Patch attached.
LGTM.
Pushed. Thanks!
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Researc
On 2021/04/15 11:54, Michael Paquier wrote:
On Wed, Apr 14, 2021 at 11:46:58PM +0900, Fujii Masao wrote:
The syntax for like_option in CREATE TABLE docs seems to forget to mention
INCLUDING COMPRESSION option. I think the following fix is necessary.
Patch attached.
-{ INCLUDING | EXCLUDING
}
+{ INCLUDING | EXCLUDING } { COMMENTS | COMPRESSION | CONSTRAINTS | DEFAULTS |
GENERATED | IDENTITY | INDEXES | STATISTICS | STORAGE | ALL }
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
diff --git a/doc/src/sgml/ref
On 2021/02/25 15:54, Michael Paquier wrote:
On Wed, Feb 24, 2021 at 08:15:59PM +0900, Fujii Masao wrote:
But I have one question; why do those commands use different
archive directories? Isn't it better to use the same one?
storage.sgml uses /var/lib/pgsql/data for the location of the
en. Others may have comments to
offer, so I'll first wait a bit before applying my suggestion from
upthread.
I agree with this change.
But I have one question; why do those commands use different
archive directories? Isn't it better to use the same one?
Regards,
--
Fujii Masao
Adva
#x27;t found the zone set for indexterm after , so you may
be right.
So you agree not to add zone attribute in this case?
Yes, I think it's nice.
So I pushed the patch. Thanks!
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
und the zone set for indexterm after , so you may
be right.
So you agree not to add zone attribute in this case?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
same situation at, for example,
the section and indexterm of pg_stat_database. If I'm missing something,
could you tell me why the zone attribute is necessary in this case?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
On 2020/11/22 6:32, Euler Taveira wrote:
On Mon, 16 Nov 2020 at 12:26, Fujii Masao mailto:masao.fu...@oss.nttdata.com>> wrote:
I found that only the following three index items have " ,"
(i.e., space + comma) in the docs. This is not harmful and
is very minor iss
according to the section
"Infinite (Unbounded) Ranges" (*1), we already call "lower/upper bound
omitted" just infinite. So I don't think the current description is incorrect.
(*1)
https://www.postgresql.org/docs/devel/rangetypes.html#RANGETYPES-INFINITE
Regards,
--
Fujii
r_participation configuration parameter , Other Planner Options
pg_trgm.strict_word_similarity_threshold configuration parameter , GUC
Parameters
pg_trgm.word_similarity_threshold configuration parameter , GUC Parameters
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research
, from the index. So what about adding
new pointer to the section for each view in the index?
Patch attached.
BTW, other stats views have both pointers in the index.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
diff
(Which is also a bit confusing, I would expect a default to apply when the
option is specified without an argument, as opposed to when the option itself
it is not specified )
As far as I recall, we discussed that in [1] and gave up doing that.
Regards,
[1]
https://postgr.es/m/1338235863.249
On 2020/09/15 16:59, Michael Paquier wrote:
On Tue, Sep 15, 2020 at 04:43:39PM +0900, Fujii Masao wrote:
So ISTM our consensus is to apply the proposed patch.
Barring any objection, I will do that.
No objections from here at the end.
Pushed. Thanks!
Regards,
--
Fujii Masao
Advanced
the doc page for file_fdw with an
extra sentence, but I agree that it is more complex to understand that
than a simple copy-paste from the doc itself.
So ISTM our consensus is to apply the proposed patch.
Barring any objection, I will do that.
Regards,
--
Fujii Masao
Advanced Computing
.
This patch fixes the DDL in the document of file-fdw.
Thanks for the patch! LGTM. I will commit it.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
er versions,
support for recovery.conf has been removed, requiring roughly the
creation of standby.signal with all recovery parameters set in
postgresql.conf if you want to set up a standby.
--
Michael
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
On 2020/06/30 14:56, Fujii Masao wrote:
On 2020/06/25 14:48, Fujii Masao wrote:
On 2020/06/25 10:00, Alvaro Herrera wrote:
On 2020-Jun-17, Fujii Masao wrote:
The document explains that restart_lsn column in pg_replication_slots view is:
The address (LSN) of oldest WAL which
On 2020/06/25 14:48, Fujii Masao wrote:
On 2020/06/25 10:00, Alvaro Herrera wrote:
On 2020-Jun-17, Fujii Masao wrote:
The document explains that restart_lsn column in pg_replication_slots view is:
The address (LSN) of oldest WAL which still might be required by
the consumer of
On 2020/06/25 10:00, Alvaro Herrera wrote:
On 2020-Jun-17, Fujii Masao wrote:
The document explains that restart_lsn column in pg_replication_slots view is:
The address (LSN) of oldest WAL which still might be required by
the consumer of this slot and thus won't be automati
On 2020/06/17 23:47, Fujii Masao wrote:
Hi,
The document explains that restart_lsn column in pg_replication_slots view is:
The address (LSN) of oldest WAL which still might be required by
the consumer of this slot and thus won't be automatically removed
during checkp
more than
max_slot_wal_keep_size from the current LSN.
Patch attached.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index 700271fd40..bf326cf533 100644
--- a/do
On 2020/06/02 14:25, Fujii Masao wrote:
On 2020/05/29 13:13, Fujii Masao wrote:
On 2020/05/28 8:43, Thomas Munro wrote:
On Wed, May 27, 2020 at 7:09 PM Simon Riggs wrote:
On Wed, 27 May 2020 at 04:27, Fujii Masao wrote:
Hi,
The group of wal_init_zero and wal_recycle is
On 2020/05/29 13:13, Fujii Masao wrote:
On 2020/05/28 8:43, Thomas Munro wrote:
On Wed, May 27, 2020 at 7:09 PM Simon Riggs wrote:
On Wed, 27 May 2020 at 04:27, Fujii Masao wrote:
Hi,
The group of wal_init_zero and wal_recycle is WAL_SETTINGS in guc.c,
but their descriptions are
1 - 100 of 124 matches
Mail list logo
