On 11/12/2025 05:06, Ashutosh Bapat wrote:
On Thu, Dec 11, 2025 at 12:49 AM Heikki Linnakangas wrote:
On 09/12/2025 14:00, Heikki Linnakangas wrote:
1. Currently, at multixid wraparound, MultiXactState->nextMXact goes to
0, which is invalid. All the readers must be prepared for that, and skip
On 05.12.2025 15:47, Tom Lane wrote:
> David Geier writes:
>> My bad. I hadn't realized that - obviously - not necessarily all code is
>> actually compiled by default.
>
>> Will the build system enable any target for which all dependencies (e.g.
>> libraries) are met, or are there targets that ne
Hi,
When reading the docs for the publication parameter
'publish_via_partition_root' [1], I felt there was too much mental
gymnastics required to understand the meaning of "the latter is the
default."
Why not just say clearly what the default value is?
PSA: a patch to do that.
==
[1]
https
At 2025-12-11 15:13:40, "Xueyu Gao" wrote:
At 2025-12-11 14:39:16, "Ioseph Kim" wrote:
>Hi
>
>TAP test codes are added in the patch
>and manual has become more user-friendly.
>
>Please review the patch and let me know if you see a better solution. I’ll be
>glad to update it accordingly.
>
>ios
On Wed, Dec 10, 2025 at 9:17 AM Gyan Sreejith wrote:
>
> Background:
>
> pg_createsubscriber currently outputs all messages (internal validation
> messages, standby server start/stop logs, recovery progress output, and
> output from utilities) directly to the console. As a result, users may find
On Thursday, December 11, 2025 3:09 PM Zhijie Hou (Fujitsu)
wrote:
> > On Tuesday, December 9, 2025 7:33 PM Amit Kapila
> > wrote
> >
> > On Mon, Dec 8, 2025 at 3:54 PM Zhijie Hou (Fujitsu)
> > wrote:
> > >
> > > On Monday, December 8, 2025 5:47 PM Amit Kapila
> > wrote:
> > > >
> > > > On Mo
Hi,
On Wed, Dec 10, 2025 at 12:22:22PM -0800, Jacob Champion wrote:
> On Wed, Dec 10, 2025 at 9:44 AM Bertrand Drouvot
> wrote:
> > Thoughts?
>
> Kneejerk reaction (as someone who wants better const-correctness!):
Thanks for sharing your thoughts!
> I suspect that this patch is not practically
Hi Hackers,
I just noticed that relation_mark_replica_identity() unconditionally opened
pg_class with RowExclusiveLock even in cases where relreplident has no
change, which incurred unnecessary relation opens, lock acquisition.
I just made a tiny refactor that defers opening pg_class until we kno
At 2025-12-11 14:39:16, "Ioseph Kim" wrote:
>Hi
>
>TAP test codes are added in the patch
>and manual has become more user-friendly.
>
>Please review the patch and let me know if you see a better solution. I’ll be
>glad to update it accordingly.
>
>ioseph
>
>On Wed, Dec 10, 2025 at 06:03:48PM +0
> -Original Message-
> From: Amit Kapila
> Sent: Tuesday, December 9, 2025 7:33 PM
> To: Hou, Zhijie/侯 志杰
> Cc: Vitaly Davydov ; pgsql-
> [email protected]; suyu.cmj ;
> tomas ; michael ;
> bharath.rupireddyforpostgres ;
> Alexander Korotkov ; Masahiko Sawada
>
> Subject: Re
Hi
TAP test codes are added in the patch
and manual has become more user-friendly.
Please review the patch and let me know if you see a better solution. I’ll be
glad to update it accordingly.
ioseph
On Wed, Dec 10, 2025 at 06:03:48PM +0900, Ioseph Kim wrote:
> Hi
>
> A failover option has bee
Laurenz Albe писал(а) 2025-12-10 16:12:
On Wed, 2025-12-10 at 15:44 +0300, Alexander Pyhalov wrote:
There's a long-standing issue with postgres_fdw - as it uses cursors,
it
prefers plans, optimized for fetching first rows. In bad scenarios
this
leads to suboptimal choice of join methods (e.g. c
On Wed, Dec 10, 2025 at 3:32 PM shveta malik wrote:
>
> +1. This can be reproduced as well. When the logical-decoding state is
> cached, we may fail to log logical-info (unassigned XID case), causing
> certain rows not to be replicated to subscribers. The steps below
> demonstrate this.
>
> Backen
čt 11. 12. 2025 v 3:53 odesílatel John Naylor
napsal:
> On Wed, Dec 10, 2025 at 5:20 PM Tomas Vondra wrote:
> > I did however notice an interesting thing - running EXPLAIN on the 99
> > queries (for 3 scales and 0/4 workers, so 6x 99) took this much time:
> >
> > master: 8s
> > master/geqo
On Thu, Dec 11, 2025 at 08:01:49AM +0900, Michael Paquier wrote:
> I still need to get through the remaining dubious changes you have
> posted, including the llvm one that was wrong. It seems like some of
> these things warrant a backpatch.
I have been looking at the rest of these changes with so
On Wed, Dec 10, 2025 at 4:23 PM Yilin Zhang wrote:
>
> Hi,
> Few comments for v34.
>
Thanks for your review!
I've addressed your comments.
As patch 0001 has been pushed. I've rebased and created a new version
v36 with the remaining patch.
regards,
Ajin Cherian
Fujitsu Australia
v36-0001-Impr
I wrote:
> Tracing suggests that the expanded array object created by the
> subscript assignment is getting flattened on the way out of the
> procedure in order to stuff it into the composite value that is the
> procedure's actual result. So that's pretty sad from a performance
> standpoint: it me
Hi All,
On Tue, Nov 18, 2025 at 4:14 PM Amit Kapila wrote:
>
> On Tue, Nov 18, 2025 at 4:05 PM Ashutosh Bapat
> wrote:
> >
> > On Tue, Nov 18, 2025 at 3:24 PM Amit Kapila wrote:
> > >
> > > On Tue, Nov 4, 2025 at 4:29 PM Ashutosh Bapat
> > > wrote:
> > > >
> > > > a. sentTxns and filteredByte
On Thu, Dec 4, 2025 at 2:39 AM Paul A Jungwirth
wrote:
>
> I think there are these cases to consider:
>
> - WITHOUT OVERLAPS on a rangetype whose subtype has a domain
> - WITHOUT OVERLAPS on a rangetype with a domain on itself
> - WITHOUT OVERLAPS on a multirangetype whose subtype has a domain
> -
> On Dec 11, 2025, at 07:35, Melanie Plageman wrote:
>
> On Tue, Dec 9, 2025 at 12:48 PM Melanie Plageman
> wrote:
>>
>> In this set 0001 and 0002 are independent. 0003-0007 are all small
>> steps toward the single change in 0007 which combines the VM updates
>> into the same WAL record as p
Hi Hackers,
While reviewing Melanie's patch [1], I found this bug where presult is not
initialized. Let me explain the logic.
In the first place:
```
static int
lazy_scan_prune(LVRelState *vacrel,
Buffer buf,
BlockNumber blkno,
Page page,
Buffer vmbuffer,
bool all_visible_according_to_vm,
bool *h
Hi, Evan
thanks for your comments.
I modified like a attached patch file.
I used pgindent, thank you.
CreateSubscriberOptions.failover is used in CREATE SUBSCRIPTION,
but LogicalRepInfos.failover is used in pg_create_logical_replication_slot()
so I left these comments as is.
ioseph
On Thu, De
On Wed, Dec 10, 2025 at 5:54 PM Amit Kapila wrote:
>
>
> 0001 looks mostly good to me. I have made minor edits in the comments
> and added error_code for one of the error messages. Please check
> attached and let me know what you think?
>
v35 looks good to me.
thanks
Shveta
On Thu, Dec 11, 2025 at 12:49 AM Heikki Linnakangas wrote:
>
> On 09/12/2025 14:00, Heikki Linnakangas wrote:
> > 1. Currently, at multixid wraparound, MultiXactState->nextMXact goes to
> > 0, which is invalid. All the readers must be prepared for that, and skip
> > over the 0. That's error-prone,
On Wed, Dec 10, 2025 at 5:20 PM Tomas Vondra wrote:
> I did however notice an interesting thing - running EXPLAIN on the 99
> queries (for 3 scales and 0/4 workers, so 6x 99) took this much time:
>
> master: 8s
> master/geqo: 20s
> master/goo: 5s
> It's nice that "goo" seems to be faster
> On Dec 11, 2025, at 09:57, Euler Taveira wrote:
>
>
>> In the “if” and “else” clauses, there are duplicate code to valid log
>> levels. We should refactor the code to avoid the duplication. For
>> example, pull up “loglevel” to the “for” loop level, then we can valid
>> it after the “if-
thanks for your comment.
There are two failover variables, one is CreateSubscriberOptions.failover, the
other is LogicalRepInfos.failover.
That comment is for LogicalRepInfos.failover.
LogicalRepInfos.failover variable is used when logical replication slot will be
created for the subscription.
On Tue, Dec 9, 2025, at 11:00 PM, Chao Li wrote:
> Now “show log_min_messages” prints the raw string the user set, in
> above example, there is not a white-space between the two log levels,
> and “show” result doesn’t have a white-space between the two log levels
> either. IMO, “SHOW log_min_mes
On Wed, Dec 10, 2025 at 5:33 PM Peter Geoghegan wrote:
> I did have a comment like that at one point, but I felt that it didn't
> quite make sense to keep it. Such a comment would address how things
> used to work, not how they work now (also how they really should have
> worked all along).
On se
On Wed, Dec 10, 2025, at 6:41 PM, Álvaro Herrera wrote:
> On 2025-Dec-10, Heikki Linnakangas wrote:
>
>> > +PG_PROCTYPE(B_AUTOVAC_LAUNCHER, "autovacuum", gettext_noop("autovacuum
>> > launcher"), AutoVacLauncherMain, true)
>> > +PG_PROCTYPE(B_AUTOVAC_WORKER, "autovacuum", gettext_noop("autovacuum
> > I can prepare the patches if there are no objections.
>
> If you could prepare a patch, that would be great! Let's do that if
> v14 and v15 can also face the issue under a high-concurrent build.
> The blast area of 6a20b04f0408 is not that bad.
"make-installcheck --jobs 8" has reproduced the
Jim Mlodgenski writes:
> I have an extension[1] that adds a collection data type using the expanded
> object API. Things perform well as it gets passed around inside a plpgsql
> function, but when passing it as an INOUT parameter, I'm hitting a double
> free.
You really need to show us your C cod
> On Dec 10, 2025, at 17:03, Ioseph Kim wrote:
>
> Hi
>
> A failover option has been added to the CREATE SUBSCRITION command, but this
> functionality isn't easily accessible using the pg_createsubscriber tool.
>
> Subscriptions created using pg_createsubscriber must be configured for
> fai
On Wed, Dec 10, 2025 at 12:48:35PM +0100, David Geier wrote:
> On 09.12.2025 23:37, Michael Paquier wrote:
>> On Fri, Dec 05, 2025 at 04:41:41PM +0900, Michael Paquier wrote:
> Do you mean in these files I forgot removing casts that got unnecessary
> after using _array() / _object()? It's possible
On Wed, Dec 10, 2025 at 4:49 AM Shlok Kyal wrote:
>
> On Mon, 24 Nov 2025 at 13:03, Peter Smith wrote:
> >
...
> > 21.
> > I was wondering if the "describe" for tables (e.g. \d+) should also
> > show the publications where the table is an ECEPT TABLE? How else is
> > the user going to know it has
On Wed, 10 Dec 2025 at 18:41, Jacob Champion
wrote:
> I think it'd be helpful for proposals to describe why a minor version
> bump was chosen over a protocol extension parameter (or vice versa),
> so that we can begin to develop some consensus.
Agreed.
> With the
> minor-version strategy, if we
On Wed, Dec 10, 2025 at 04:39:11PM -0600, Sami Imseih wrote:
> On 15 STABLE, I encountered the same issue [0] which was fixed in 6a20b04f0408
> starting from 16. It seems like a decision not to backpatch to lower
> versions at the time was due to a lack of reports [1], but I think since we
> have
On Mon, Dec 08, 2025 at 04:19:54PM -0500, Robert Haas wrote:
> I took a brief look at this today, looking at parts of v8-0005 and
> v8-0015.
Thanks for the input!
> Although I don't dislike the idea of an abstraction layer in
> concept, it's unclear to me how much this particular abstraction laye
Hi Shlok -
Here are some review comments for v31-0001 (EXCEPT (tablelist))
==
Commit message
1.
The new syntax allows specifying excluded relations when creating or altering
a publication. For example:
CREATE PUBLICATION pub1 FOR ALL TABLES EXCEPT TABLE (t1,t2);
~
In v30, you removed all t
Hi,
On 15 STABLE, I encountered the same issue [0] which was fixed in 6a20b04f0408
starting from 16. It seems like a decision not to backpatch to lower
versions at the
time was due to a lack of reports [1], but I think since we have to
support 14 and 15 for
a few more years, it makes sense to. I c
On Tue, 9 Dec 2025 at 21:08, Hannu Krosing wrote:
>
> On Tue, Dec 9, 2025 at 7:41 PM Matthias van de Meent
> wrote:
> >
> > On Mon, 8 Dec 2025 at 16:25, Hannu Krosing wrote:
> > > Suggestion to "get the user specify their own identity column" sounds
> > > good in purely theoretical sense, but ca
On Wed, Dec 10, 2025 at 2:41 PM Victor Yegorov wrote:
> Compiled and tested without issues.
Pushed. Thanks for the review!
> Small note: as you're removing “We rely on the convention that heap TIDs in
> the scanpos
> items array are stored in ascending heap TID order…” part of the comment,
> p
>
> Overall, I think this patch is doing a good thing. Also, are we
> holding it until the next SQL standard release, because sql/23 leaks
> this feature?
>
The impression that I get is that the SQL Standard has become more
descriptive and less prescriptive. It takes things that exist and
builds t
On 2025-Dec-10, Heikki Linnakangas wrote:
> On 10/12/2025 15:45, Álvaro Herrera wrote:
> > Hello,
> >
> > Pursuant to my comments in [1], I attach a patch that restricts the use
> > of translated process types as indicated in $SUBJECT. This adds a
> > separate column to the process type list, mo
On Thu, Dec 11, 2025 at 5:32 AM Greg Burd wrote:
> Rebased with only minor changes to meson.build this patch is ready for
> review/commit as it is passing tests on my aarch64 Win11 MSVC system. Also
> note that this system I'm testing on is ready to become a member of the
> buildfarm (applicat
On Wed, Dec 10, 2025 at 4:09 PM Corey Huinker wrote:
> I think the change would be worth the destabilization, because it makes it so
> much easier to talk about complex query plans. Additionally, it would make it
> reasonable to programmatically extract portions of a plan, allowing for much
> m
I wrote:
> Encoding-specific behaviors might be worth testing later, but
> I'm not excited about that personally.
Despite that disclaimer, I experimented with the questionable nb.po
file on my OpenIndiana installation, and it seems to Just Work
after creating the nb_NO.UTF-8 -> nb locale symlink:
On Wed, 10 Dec 2025 at 21:02, Jacob Champion
wrote:
>
> (To call it out explicitly: I work with Ajit, and I asked him to take
> a look at GoAway, and I'm particularly interested in the
> "reauthenticate or else" case. Let me know if any of that is
> problematic -- or if anyone's worried that it wi
On Wed, Dec 10, 2025 at 9:54 AM Robert Haas wrote:
> On Wed, Dec 10, 2025 at 6:20 AM Amit Langote
> wrote:
> > These are just high-level comments after browsing the patches and
> > reading some bits like pgpa_identifier to get myself familiarized with
> > the project. I like that the key concep
On 12/8/2025 10:48 AM, Robert Haas wrote:
> On Sat, Dec 6, 2025 at 2:08 AM Bryan Green wrote:
>>> I think I'm missing something obvious here. call_string_check_hook
>>> doesn't do any memory context management - it just calls the hook.
>
> No, it does do memory management. It has a PG_TRY()/PG_CA
On Wed, Dec 10, 2025 at 9:44 AM Bertrand Drouvot
wrote:
> Thoughts?
Kneejerk reaction (as someone who wants better const-correctness!): I
suspect that this patch is not practically reviewable for most people.
Especially knowing that the patchset was formed via subtraction of
known-bad cases rathe
Hi,
Patches don't apply anymore.
Could you rebase it please ?
Thank you so much to all of you for your persistence.
Stéphane.
Back.
Le mer. 10 déc. 2025 à 00:54, Alexander Korotkov
a écrit :
>
> On Wed, Dec 10, 2025 at 1:22 AM Dmitry Koval wrote:
> > Thank you for your corrections!
> > Two que
(To call it out explicitly: I work with Ajit, and I asked him to take
a look at GoAway, and I'm particularly interested in the
"reauthenticate or else" case. Let me know if any of that is
problematic -- or if anyone's worried that it will become so -- so I
can course-correct sooner rather than late
ср, 10 дек. 2025 г. в 21:40, Peter Geoghegan :
> Attached v5 avoids the regression by tweaking _bt_readpage. I will
> commit this version soon (I really mean it this time!).
>
> …
>
> I also gave up on the idea of using a bitmapset for v5 -- the issue
> with regressing _bt_readpage discouraged me
=?utf-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= writes:
> Digging a bit more in the history of **/nb.po, there seems to be a
> policy that files that are less than 80% translated are removed¹,
BTW, while the wiki page does still say that, I have a vague idea
that the policy might have been changed late
On 09/12/2025 14:00, Heikki Linnakangas wrote:
1. Currently, at multixid wraparound, MultiXactState->nextMXact goes to
0, which is invalid. All the readers must be prepared for that, and skip
over the 0. That's error-prone, we've already missed that a few times.
Let's change things so that the
I wrote:
> Peter Eisentraut writes:
>> How would one know all the country codes to create links for?
> Yeah, I've been wrestling with that question. The best idea
> I have at the moment is to look at "locale -a" output to see
> which country codes Solaris thinks there are for each language,
> an
On Wed, Dec 3, 2025 at 10:18 AM Victor Yegorov wrote:
> Patch looks fine, applies and compiles cleanly, passes tests.
This patch was trickier than initially expected. I paid no attention
to the possible downside of changing the posting list iteration code
in _bt_readpage (i.e. from scan posting l
I have an extension[1] that adds a collection data type using the expanded
object API. Things perform well as it gets passed around inside a plpgsql
function, but when passing it as an INOUT parameter, I'm hitting a double
free. It looks like the object gets transferred to the context of the
proced
On Wed Dec 10, 2025 at 8:32 AM CST, Srirama Kucherlapati wrote:
> We encountered the following error when building without the "_static" suffix
> in the library name:
> Found ninja-1.12.1 at /opt/freeware/bin/ninja
> ERROR: Multiple producers for Ninja target
> "src/interfaces/ecpg/compat
> Now, it is kind of true that the STATS_WRITE case feels a bit
> disturbing written this way: we let a module take an action, but we
> don't actually know the state of the main pgstats file when inside the
> callback. I mean, you can know how things are going on, but it means
> that a module can
Hi,
While working on a patch to set the VM in the same WAL record as
pruning and freezing [1], I discovered we have no test coverage of the
case where vacuum phase I sets the VM but no modifications are made to
the heap buffer (not even setting PD_ALL_VISIBLE). This can only
happen when the VM was
Hi,
One of our customers has this workload where every so often they
update the whole table to make sure it's up-to-date. In general, you'd
probably want to use MERGE for such a workload and ignore all rows
that already have only matching data, but there's a catch: PostgreSQL
doesn't have an effic
On Thu, Nov 27, 2025 at 5:50 AM Rafia Sabih wrote:
> Thanks Kenan for these. So, it looks like the patch performs the same as in
> the local scan case. I wonder if you found any case of performance
> degradation with the patch.
>
> Per an off-list discussion with Robert, he suggested using the e
On Mon, Dec 8, 2025 at 1:43 PM Jelte Fennema-Nio wrote:
> 1. We still have fairly limited experience with protocol options, so
> afaik not everyone agrees what we should use a version bump for vs a
> protocol extension.
I think it'd be helpful for proposals to describe why a minor version
bump wa
On 25/08/2025 04:05, Chao Li wrote:
On Aug 25, 2025, at 08:00, jian he wrote:
in src/test/modules/test_ddl_deparse/sql/alter_table.sql:
The test initially focuses on the "parent" table, then switches to the
"part"
table, and goes back to the "parent" table.
This seems weird? so I slight
Hi,
Thanks for raising this. I did not look at the patch, but I have some high
level comments.
> I would like to propose adding a last_executed timestamptz column to
> pg_stat_statements. This column records when each tracked statement
> was most recently executed.
I do think there is value in a
Melanie Plageman writes:
>
> Thanks for working on this, Renan.
>
Thanks for the feedback.
> It is quite a large patch set, which makes sense because we do not
> have histogram types in any of the shared memory stats right now. I
> think if we want to go the route of adding a histogram, we might
=?utf-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= writes:
> Álvaro Herrera writes:
>> Oh. Well, that's clearly a process failure, and the fix will require us
>> deleting that file on all branches from 16 and up anyway, so I have no
>> issues with the plan of requiring all message catalogs to be UTF-8.
On Wed, Dec 10, 2025 at 05:02:14PM +0100, Peter Eisentraut wrote:
> On 09.12.25 22:22, Tom Lane wrote:
> > At least Solaris is kind enough to let you do that with
> > symlinks [2], so that after
> >
> > cd $INSTALLATION/share/locale
> > ln -s es es_ES.UTF-8
> >
> > translation starts work
Hello.
Rebased with only minor changes to meson.build this patch is ready for
review/commit as it is passing tests on my aarch64 Win11 MSVC system. Also
note that this system I'm testing on is ready to become a member of the
buildfarm (application submitted) and monitor this combo in perpetuit
On 10/12/2025 15:45, Álvaro Herrera wrote:
Hello,
Pursuant to my comments in [1], I attach a patch that restricts the use
of translated process types as indicated in $SUBJECT. This adds a
separate column to the process type list, mostly extracted from Euler's
patch, not marked for translation,
Peter Eisentraut writes:
> On 09.12.25 22:22, Tom Lane wrote:
>> At least Solaris is kind enough to let you do that with
>> symlinks [2], so that after
>> cd $INSTALLATION/share/locale
>> ln -s es es_ES.UTF-8
>> translation starts working for that particular value of
>> lc_messages.
> H
On 09.12.25 22:22, Tom Lane wrote:
At least Solaris is kind enough to let you do that with
symlinks [2], so that after
cd $INSTALLATION/share/locale
ln -s es es_ES.UTF-8
translation starts working for that particular value of
lc_messages.
This policy dictates making a rather la
Hello,
I would like to propose adding a last_executed timestamptz column to
pg_stat_statements. This column records when each tracked statement
was most recently executed.
The motivation comes from real world experience with monitoring tools
like pgwatch that poll pg_stat_statements regularly. Cu
On Tue, Dec 9, 2025 at 6:08 PM Andres Freund wrote:
> On 2025-12-09 16:40:17 -0500, Robert Haas wrote:
> > On Fri, Aug 29, 2025 at 4:38 AM Julien Tachoires
> > wrote:
> > Potentially, there could be a performance problem
>
> I think the big performance hazard with this is repeated deforming. The
=?utf-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= writes:
> Looking at the translations repo, there's 30 .po files (out of 530) that
> are not UTF-8, but I guess only nb/pg_config.po meets the 80% threshold
> and makes it into the main repo. To avoid future breakage, should we
> ask the translation team
Tom Lane writes:
> =?utf-8?Q?=C3=81lvaro?= Herrera writes:
>
>> Oh. Well, that's clearly a process failure, and the fix will require us
>> deleting that file on all branches from 16 and up anyway, so I have no
>> issues with the plan of requiring all message catalogs to be UTF-8.
>
> Shall I ju
Álvaro Herrera writes:
> On 2025-Dec-10, Dagfinn Ilmari Mannsåker wrote:
>
>> Álvaro Herrera writes:
>
>> > Hmm, where do you see that file? It was removed by commit 3c70de2e12b9
>> > from branch 12 in 2019, and has never existed since.
>>
>> That translation commit was on the REL_12_STABLE br
=?utf-8?Q?=C3=81lvaro?= Herrera writes:
> On 2025-Dec-10, Dagfinn Ilmari Mannsåker wrote:
>> That translation commit was on the REL_12_STABLE branch, after it was
>> cut from master (after rc1, even). Looking more closely, the
>> post-branch translation updates deleted it from version 12, 13, 14,
On Wed, Sep 24, 2025 at 9:06 AM Alexandra Wang
wrote:
>
> The rest of your feedback I've made changes accordingly as you suggested.
>
> Best,
> Alex
>
hi.
+
+ PostgreSQL implements the JSON simplified accessor as specified in SQL:2023.
not sure we need to decorated SQL:2023 as SQL:2023,
but
Hi,
On 2025-12-10 11:51:35 +0200, Heikki Linnakangas wrote:
> On 10/12/2025 01:33, Matthias van de Meent wrote:
> > Hi Heikki, Andres,
> >
> > Whilst looking through catcache.c's code I noticed this piece of code:
> >
> > ReleaseCatCacheListWithOwner(CatCList *list, ResourceOwner resowner)
> > {
On Wed, Dec 10, 2025 at 6:20 AM Amit Langote wrote:
> These are just high-level comments after browsing the patches and
> reading some bits like pgpa_identifier to get myself familiarized with
> the project. I like that the key concept here is plan stability
> rather than plan control, because th
On 2025-Dec-10, Dagfinn Ilmari Mannsåker wrote:
> Álvaro Herrera writes:
> > Hmm, where do you see that file? It was removed by commit 3c70de2e12b9
> > from branch 12 in 2019, and has never existed since.
>
> That translation commit was on the REL_12_STABLE branch, after it was
> cut from mast
Hi Tristan,
Thank you for reviewing the patch.
We encountered the following error when building without the "_static" suffix
in the library name:
Found ninja-1.12.1 at /opt/freeware/bin/ninja
ERROR: Multiple producers for Ninja target
"src/interfaces/ecpg/compatlib/libecpg_compat.a”.
Álvaro Herrera writes:
> On 2025-Dec-09, Tom Lane wrote:
>
>> If you're right about Sun not doing transcoding, then I guess we would
>> only need to create symlinks matching the encodings used in our .po
>> files, which'd remove the symlink bloat problem and replace it with
>> how-do-we-extract-t
Hello,
Pursuant to my comments in [1], I attach a patch that restricts the use
of translated process types as indicated in $SUBJECT. This adds a
separate column to the process type list, mostly extracted from Euler's
patch, not marked for translation, and uses it in a couple of places.
I think th
On 2025-Dec-09, Tom Lane wrote:
> If you're right about Sun not doing transcoding, then I guess we would
> only need to create symlinks matching the encodings used in our .po
> files, which'd remove the symlink bloat problem and replace it with
> how-do-we-extract-that-encoding-name ... although i
On Tue, Dec 9, 2025 at 12:18 AM Mahendra Singh Thalor
wrote:
> On Mon, 8 Dec 2025 at 22:39, tushar wrote:
>
> Here, I am attaching an updated patch for the review and testing. This
> can be applied on commit d0d0ba6cf66c4043501f6f7.
>
>
Thanks, Mahendra, please refer to this scenario where if
"
On 10/12/2025 13:15, Shlok Kyal wrote:
Hi,
While working on the thread [1], we found that the comment in the
function GetPublicationRelations is not correct. This function gets
the list of relations associated with the publication, but the comment
says the opposite :
/* Find all publications ass
> On Dec 10, 2025, at 20:23, Amit Kapila wrote:
>
> On Wed, Dec 10, 2025 at 10:37 AM Ajin Cherian wrote:
>>
>> Attaching v34 addressing the above comments.
>>
>
> 0001 looks mostly good to me. I have made minor edits in the comments
> and added error_code for one of the error messages. Ple
On Wed, Dec 10, 2025 at 6:43 AM Jakub Wartak
wrote:
> Quick-question regarding cross-interactions of the extensions: would
> it be possible for auto_explain to have something like
> auto_explain.log_custom_options='PLAN_ADVICES' so that it could be
> dumping the advice of the queries involved
Yes
On Wed, 10 Dec 2025 at 13:58, jian he wrote:
>
> On Tue, Dec 9, 2025 at 11:39 AM jian he wrote:
> >
> > On Mon, Dec 1, 2025 at 1:41 PM Corey Huinker
> > wrote:
> > >>
> > > No, I meant implementing the syntax for being able to declare a custom
> > > CAST function as safe (or not). Basically ad
> On Dec 10, 2025, at 19:15, Shlok Kyal wrote:
>
> Hi,
>
> While working on the thread [1], we found that the comment in the
> function GetPublicationRelations is not correct. This function gets
> the list of relations associated with the publication, but the comment
> says the opposite :
> /
On 10/12/2025 14:32, Potapov Alexander wrote:
Hello,
This is about the TAP test src/test/postmaster/t/003_start_stop.pl. The test contains a loop that performs 21 iterations in order to use all possible connection slots. We could calculate the number of available connections more accurately. I
On Wed, 2025-12-10 at 15:44 +0300, Alexander Pyhalov wrote:
> There's a long-standing issue with postgres_fdw - as it uses cursors, it
> prefers plans, optimized for fetching first rows. In bad scenarios this
> leads to suboptimal choice of join methods (e.g. choosing nest loop over
> hash join)
Hello,
This is about the TAP test src/test/postmaster/t/003_start_stop.pl. The test
contains a loop that performs 21 iterations in order to use all possible
connection slots. We could calculate the number of available connections more
accurately. It relates to the size of backend pool that is
Hi.
There's a long-standing issue with postgres_fdw - as it uses cursors, it
prefers plans, optimized for fetching first rows. In bad scenarios this
leads to suboptimal choice of join methods (e.g. choosing nest loop over
hash join) on remote side. I've crafted WIP patch, which tries to fix
t
On Wed, Dec 10, 2025 at 10:37 AM Ajin Cherian wrote:
>
> Attaching v34 addressing the above comments.
>
0001 looks mostly good to me. I have made minor edits in the comments
and added error_code for one of the error messages. Please check
attached and let me know what you think?
--
With Regards
Hi,
On Wed, 10 Dec 2025 at 01:13, Manni Wood wrote:
>
> Bilal Yavuz (Nazir Bilal Yavuz?),
It is Nazir Bilal Yavuz, I changed some settings on my phone and it
seems that it affected my mail account, hopefully it should be fixed
now.
> I did not get a chance to do any work on this today, but want
1 - 100 of 117 matches
Mail list logo
