On Thu, Dec 9, 2021 at 5:22 PM Michael Paquier wrote:
>
> On Wed, Dec 08, 2021 at 05:47:39PM -0700, David G. Johnston wrote:
> > Yeah, I was treating the leading dash as being silent...the syntax dash(es)
> > for single and multi-character arguments seems unimportant to read aloud in
> > the gener
On Mon, Dec 6, 2021 at 9:17 PM Thomas Munro wrote:
> On Sat, Dec 4, 2021 at 6:18 PM Thomas Munro wrote:
> > I think this was broken by WIN32_LEAN_AND_MEAN (and since gained a
> > merge conflict, but that's easy to fix). I'll try to figure out the
> > right system header hacks to unbreak it...
>
On Wed, Dec 08, 2021 at 01:23:51PM +0100, Peter Eisentraut wrote:
> I wasn't really aware of this script either. But I think it's a good idea
> to have it. But only if it's run automatically as part of a test suite run.
Okay. If we do that, I am wondering whether it would be better to
rewrite t
On Thu, Dec 9, 2021 at 4:02 PM Michael Paquier wrote:
>
> On Wed, Dec 08, 2021 at 05:03:30PM +0900, Masahiko Sawada wrote:
> > Agreed. I've attached an updated patch that incorporated your review
> > comments. Please review it.
>
> That looks correct to me. One thing that I have noticed while
> r
On Thu, Dec 9, 2021 at 11:47 AM Amit Kapila wrote:
>
> On Wed, Dec 8, 2021 at 4:36 PM Masahiko Sawada wrote:
> >
> > On Wed, Dec 8, 2021 at 5:54 PM Amit Kapila wrote:
> > >
> > > On Wed, Dec 8, 2021 at 12:36 PM Masahiko Sawada
> > > wrote:
> > > >
> > > > On Wed, Dec 8, 2021 at 3:50 PM Amit Ka
On Thu, Dec 9, 2021 at 2:24 PM Masahiko Sawada wrote:
>
> On Thu, Dec 9, 2021 at 11:47 AM Amit Kapila wrote:
> >
> > I am thinking that we can start a transaction, update the catalog,
> > commit that transaction. Then start a new one to update
> > origin_lsn/timestamp, finishprepared, and commit
On 02.12.21 08:20, Peter Eisentraut wrote:
Buildfarm impact:
gaur and prariedog use Python 2.6 and would need to be upgraded.
Tom, are you planning to update the Python version on these build farm
members? I realize these are very slow machines and this might take
some time; I'm just wonder
On 12/9/21 01:12, Jacob Champion wrote:
> On Wed, 2021-12-08 at 02:58 +0100, Tomas Vondra wrote:
>>
>> On 12/8/21 00:26, Jacob Champion wrote:
>>> On Tue, 2021-12-07 at 22:21 +0100, Tomas Vondra wrote:
IMO it's impossible to solve this attack within TCE, because it requires
ensuring c
On Mon, Dec 6, 2021 at 10:17 AM Amit Kapila wrote:
>
> On Fri, Dec 3, 2021 at 6:06 PM Masahiko Sawada wrote:
> >
> > On Fri, Dec 3, 2021 at 6:03 PM Amit Kapila wrote:
> > >
> > > On Thu, Dec 2, 2021 at 6:01 PM Masahiko Sawada
> > > wrote:
> > > >
> > > > I've attached updated patches.
> > > >
On Thu, Dec 9, 2021 at 3:35 PM Amit Kapila wrote:
>
> On Mon, Dec 6, 2021 at 10:17 AM Amit Kapila wrote:
> >
> > On Fri, Dec 3, 2021 at 6:06 PM Masahiko Sawada
> > wrote:
> > > > 2. The patch seems to be calling parallel_vacuum_should_skip_index
> > > > thrice even before starting parallel vacu
On Wed, Dec 8, 2021 at 11:38 AM Amit Kapila wrote:
>
> On Wed, Dec 8, 2021 at 11:30 AM vignesh C wrote:
> >
> > On Wed, Dec 8, 2021 at 11:11 AM Amit Kapila wrote:
> > >
> > > On Tue, Dec 7, 2021 at 5:53 PM vignesh C wrote:
> > > >
> > > > On Fri, Dec 3, 2021 at 11:24 AM houzj.f...@fujitsu.com
>
Dear Fujii-san
Thank you for quick reviewing! I attached new ones.
> Regarding 0001 patch, IMO it's better to explain that
> postgres_fdw.application_name can be any string of any length and contain even
> non-ASCII characters, unlike application_name. So how about using the
> following
> descri
On Thu, Dec 9, 2021 at 7:05 PM Amit Kapila wrote:
>
> On Mon, Dec 6, 2021 at 10:17 AM Amit Kapila wrote:
> >
> > On Fri, Dec 3, 2021 at 6:06 PM Masahiko Sawada
> > wrote:
> > >
> > > On Fri, Dec 3, 2021 at 6:03 PM Amit Kapila
> > > wrote:
> > > >
> > > > On Thu, Dec 2, 2021 at 6:01 PM Masahik
On 2021-Dec-09, Bharath Rupireddy wrote:
> I just want to call this out: an insertion of 10 million rows in the
> primary generates a bunch of messages in the standby [1] within 40 sec
> (size of the standby server log grows by 5K).
Hmm, that does sound excessive to me in terms of log bloat incre
"Applications using this level must be prepared to retry transactions
due to serialization failures."
...
"When an application receives this error message, it should abort the
current transaction and retry the whole transaction from the
beginning."
I note that the specific error codes this applies
On Thu, Dec 9, 2021 at 12:43 PM Amul Sul wrote:
>
> On Thu, Dec 9, 2021 at 12:03 PM Amit Langote wrote:
> >
> > On Thu, Dec 9, 2021 at 3:12 PM Amul Sul wrote:
> > > On Thu, Dec 9, 2021 at 11:24 AM Amit Langote
> > > wrote:
> > > >
> > > []
> > > > On Mon, Dec 6, 2021 at 10:57 PM Nitin Jadh
On 12/8/21 18:10, Thomas Munro wrote:
> On Sun, Dec 5, 2021 at 4:16 AM Andrew Dunstan wrote:
>> TAP tests are passed a path to pg_regress as $ENV{PG_REGRESS}. You
>> should be using that. On non-MSVC, the path to a non-installed psql is
>> in this case "$TESTDIR/../../bin/psql" - this should wo
On 03.12.21 21:13, Tom Lane wrote:
Andrew Dunstan writes:
On 12/3/21 14:42, Tom Lane wrote:
Right, I envisioned that ASCII behaves the same but we'd use
a numeric representation for high-bit-set values. These
cases could be told apart fairly easily by charin(), since
the numeric representatio
Peter Eisentraut writes:
> On 02.12.21 08:20, Peter Eisentraut wrote:
>> Buildfarm impact:
>> gaur and prariedog use Python 2.6 and would need to be upgraded.
> Tom, are you planning to update the Python version on these build farm
> members? I realize these are very slow machines and this migh
On 09.12.21 03:44, Thomas Munro wrote:
On Thu, Dec 9, 2021 at 11:46 AM Andres Freund wrote:
Is it perhaps time to to use unix sockets on windows by default
(i.e. PG_TEST_USE_UNIX_SOCKETS), at least when on a new enough windows?
Makes sense to get this to work, at least as an option.
Makes s
Peter Eisentraut writes:
> I think we could consider char to be a single-byte bytea and use the
> escape format of bytea for char. That way there is some precedent and
> we don't add yet another encoding or escape format.
Do you want to take that as far as changing backslash to print
as '\\' ?
On Thu, Dec 9, 2021 at 11:12 AM Ashutosh Sharma
wrote:
> Hi,
>
> The issue here is that we are trying to create a table that exists inside
> a non-default tablespace when doing ALTER DATABASE. I think this should be
> skipped otherwise we will come across the error like shown below:
>
> ashu@post
Hi there,
I played a lot with frama-c a long time ago.
Frama-c annotations are very verbose and the result is highly dependent on
the skills of the annotator.
Keeping it up-to-date on such a large project with high-speed development
will be, in my very humble opinion, extremely difficult.
Perhaps
On 06.12.21 22:19, Tom Lane wrote:
A minimal amount of maintenance would be "only back-patch fixes
for issues that cause failure-to-build". The next step up is "fix
issues that cause failure-to-pass-regression-tests", and then above
that is "fix developer-facing annoyances, such as compiler warn
On Thu, Dec 9, 2021 at 7:23 PM Neha Sharma wrote:
>
> On Thu, Dec 9, 2021 at 11:12 AM Ashutosh Sharma wrote:
> \c postgres
> alter database test1 set tablespace tab1;
>
> --Cancel the below command after few seconds
> alter database test1 set tablespace pg_default;
>
> \c test1
> alter table t s
On Thu, Sep 16, 2021 at 8:23 PM Andrew Dunstan wrote:
>
> On 9/14/21 8:55 AM, Andrew Dunstan wrote:
>
I have tried with few of the test cases of constructor function, wanted to
check on the below scenarios:
1)
Why we don't support KEY(however is optional as per SQL standard) keyword?
SELECT JS
On 12/9/21 08:35, Peter Eisentraut wrote:
> On 09.12.21 03:44, Thomas Munro wrote:
>> On Thu, Dec 9, 2021 at 11:46 AM Andres Freund
>> wrote:
>>> Is it perhaps time to to use unix sockets on windows by default
>>> (i.e. PG_TEST_USE_UNIX_SOCKETS), at least when on a new enough windows?
>
> Makes
On 12/8/21 20:03, Andres Freund wrote:
>
> I wonder if we need a host2unix() helper accompanying perl2host()? Seems nicer
> than sprinkling s!\\!/!g if $PostgreSQL::Test::Utils::windows_os in a growing
> number of places...
>
Probably a good idea. I would call it canonical_path or something like
On 09.12.21 15:04, Himanshu Upadhyaya wrote:
1)
Why we don't support KEY(however is optional as per SQL standard) keyword?
SELECT JSON_OBJECT(KEY 'a' VALUE '123');
ERROR: type "key" does not exist
LINE 1: SELECT JSON_OBJECT(KEY 'a' VALUE '123');
ORACLE is supporting the above syntax.
I can see
On 07.12.21 19:49, Jacob Champion wrote:
= Implicit TLS =
Reactions to implicit TLS were mixed, from "we should not do this" to
"it might be nice to have the option, from a technical standpoint".
Both a separate-port model and a shared-port model were tentatively
proposed. The general consensus
On 07.12.21 21:24, Tom Lane wrote:
I wrote:
Peter Eisentraut writes:
Could we add explicit casts (like polcmd::text) here? Or would it break
too much?
I assumed it'd break too much to consider doing that. But I suppose
that since a typcategory change would be initdb-forcing anyway, maybe
it
Hi! Thanks for the quick reply. Are you doing any of this work in a
public repository? If so, could we have a link? There is a similar
idea in Java Modelling Language. It also uses its own annotations to
describe additional requirements. Are you considering to use it? Maybe
I could help...
On Wed
Thank you very much Tom for your quick reply! If nobody objects to it
too much, I'd focus my work on ensuring full-text-search is
memory-safe.
On Wed, 8 Dec 2021 at 15:21, Tom Lane wrote:
>
> Colin Gilbert writes:
> > I've been becoming more and more interested in learning formal methods
> > and
On Tue, Nov 30, 2021 at 6:55 AM Amit Kapila wrote:
> > This patch does detect ownership changes more quickly (at the
> > transaction boundary) than the current code (only when it reloads for
> > some other reason). Transaction boundary seems like a reasonable time
> > to detect the change to me.
>
On Thu, Dec 9, 2021 at 1:02 PM Maciek Sakrejda wrote:
>
> On Wed, Dec 1, 2021 at 5:15 AM Tom Lane wrote:
> >
> > Justin Pryzby writes:
> > > +1 to document it, but it seems like the worse problem is allowing the
> > > admin to
> > > write a configuration which causes the server to fail to start
On Wed, Dec 8, 2021 at 11:58 PM Amit Kapila wrote:
> But, I think as soon as we are trying to fix (b), we seem to be
> allowing non-superusers to apply changes. If we want to do that then
> we should be even allowed to change the owners to non-superusers. I
> was thinking of the below order:
> 1.
On Thu, Dec 9, 2021 at 6:00 PM Alvaro Herrera wrote:
>
> On 2021-Dec-09, Bharath Rupireddy wrote:
>
> > I just want to call this out: an insertion of 10 million rows in the
> > primary generates a bunch of messages in the standby [1] within 40 sec
> > (size of the standby server log grows by 5K).
On 08.12.21 18:31, Tom Lane wrote:
A question that seems pretty relevant here is: what exactly is the
point of using the subtest feature, if we aren't especially interested
in its effect on the overall test count? I can see that it'd have
value when you wanted to use skip_all to control a subset
On Thu, Dec 09, 2021 at 05:17:54PM +0900, Michael Paquier wrote:
> On Wed, Dec 08, 2021 at 01:23:51PM +0100, Peter Eisentraut wrote:
> > I wasn't really aware of this script either. But I think it's a good idea
> > to have it. But only if it's run automatically as part of a test suite run.
>
> O
On 2021-Dec-09, Bharath Rupireddy wrote:
> On Thu, Dec 9, 2021 at 6:00 PM Alvaro Herrera wrote:
> >
> > On 2021-Dec-09, Bharath Rupireddy wrote:
> >
> > > I just want to call this out: an insertion of 10 million rows in the
> > > primary generates a bunch of messages in the standby [1] within 40
On Wed, Nov 10, 2021 at 8:51 PM Robert Haas wrote:
>
> On Thu, Nov 4, 2021 at 1:49 PM Bharath Rupireddy
> wrote:
> > Please review the attached v2 patch.
>
> It looks OK to me.
May I know if the v2 patch (attached at [1] in this thread) is still
of interest?
CF entry is here - https://commitfes
> On Dec 8, 2021, at 8:09 PM, Amit Kapila wrote:
>
> So, do you agree that we can disable the subscription on any error if
> this parameter is set?
Yes, I think that is fine. We can commit it that way, and revisit the issue
for v16 if it becomes a problem in practice.
—
Mark Dilger
Enterpr
> On Dec 9, 2021, at 7:41 AM, Robert Haas wrote:
>
> On Tue, Nov 30, 2021 at 6:55 AM Amit Kapila wrote:
>>> This patch does detect ownership changes more quickly (at the
>>> transaction boundary) than the current code (only when it reloads for
>>> some other reason). Transaction boundary seem
> On Dec 9, 2021, at 7:47 AM, Robert Haas wrote:
>
> 1 and 2B seem to require changing the same code, or related code. 1A
> seems to require a completely different set of changes. If I'm right
> about that, it seems like a good reason for doing 1+2B first and
> leaving 2A for a separate patch.
[ mostly for the archives' sake ]
I wrote:
> I ran a new set of experiments concerning building back branches
> on modern platforms, this time trying Fedora 35 (gcc 11.2.1)
> on x86_64. I widened the scope of the testing a bit by adding
> "--enable-nls --with-perl" and running check-world not jus
This is a longer-term plan and I'm going to practice a lot on my own
projects prior. I'm just sending out feelers. My main idea was to
annotate parts of the code that have already been well-established and
validate it while trying to uncover potential edge-cases. I'll do that
at home until somethin
On 12/09/21 12:53, Colin Gilbert wrote:
> ... plugins written in
> something like Rust or Ada/SPARK? I write this, hoping not to tread on
Some work toward supporting "deep" PostgreSQL extensions in Rust
was presented at PGCon 2019 [0].
Regards,
-Chap
[0] https://www.pgcon.org/2019/schedule/even
Chapman Flack writes:
> On 12/09/21 12:53, Colin Gilbert wrote:
>> ... plugins written in
>> something like Rust or Ada/SPARK? I write this, hoping not to tread on
>
> Some work toward supporting "deep" PostgreSQL extensions in Rust
> was presented at PGCon 2019 [0].
There's also https://github.
On 2021/12/09 19:52, kuroda.hay...@fujitsu.com wrote:
Dear Fujii-san
Thank you for quick reviewing! I attached new ones.
Thanks for updating the patches!
Regarding 0001 patch, IMO it's better to explain that
postgres_fdw.application_name can be any string of any length and contain even
no
Hi,
On 2021-12-09 14:35:37 +0100, Peter Eisentraut wrote:
> On 09.12.21 03:44, Thomas Munro wrote:
> > On Thu, Dec 9, 2021 at 11:46 AM Andres Freund wrote:
> > > Is it perhaps time to to use unix sockets on windows by default
> > > (i.e. PG_TEST_USE_UNIX_SOCKETS), at least when on a new enough wi
Hi,
On 2021-12-03 15:02:24 -0500, Melanie Plageman wrote:
> From e0f7f3dfd60a68fa01f3c023bcdb69305ade3738 Mon Sep 17 00:00:00 2001
> From: Melanie Plageman
> Date: Mon, 11 Oct 2021 16:15:06 -0400
> Subject: [PATCH v17 1/7] Read-only atomic backend write function
>
> For counters in shared memory
When a user must shut down and restart in single-user mode to run
vacuum on an entire database, that does a lot of work that's
unnecessary for getting the system online again, even without
index_cleanup. We had a recent case where a single-user vacuum took
around 3 days to complete.
Now that we ha
Hi,
On 2021-11-19 15:11:57 -0500, Melanie Plageman wrote:
> From 2130175c5d794f60c5f15d6eb1b626c81fb7c39b Mon Sep 17 00:00:00 2001
> From: Melanie Plageman
> Date: Thu, 15 Apr 2021 07:01:01 -0400
> Subject: [PATCH v2] Index build avoids immed fsync
>
> Avoid immediate fsync for just built indexe
Hi,
On 2021-12-09 08:12:14 -0500, Andrew Dunstan wrote:
> > Does anyone want to object to the concept of the "pg_user_files"
> > directory or the developer-only GUC "allow_relative_tablespaces"?
> > There's room for discussion about names; maybe initdb shouldn't create
> > the directory unless you
On Fri, Dec 10, 2021 at 2:12 AM Andrew Dunstan wrote:
> The new version appears to set an empty --bindir for pg_regress. Is that
> right?
It seems to be necessary to find eg psql, since --bindir='' means
"expect $PATH to contain the installed binaries", and that's working
on both build systems.
On 12/9/21, 11:34 AM, "John Naylor" wrote:
> When a user must shut down and restart in single-user mode to run
> vacuum on an entire database, that does a lot of work that's
> unnecessary for getting the system online again, even without
> index_cleanup. We had a recent case where a single-user va
> On 8 Dec 2021, at 16:25, Tom Lane wrote:
> I think the main point is to make sure that the test script reached an
> intended exit point, rather than dying early someplace. It's not apparent
> to me why reaching a done_testing() call is a less reliable indicator of
> that than executing some sp
On Thu, Dec 9, 2021 at 11:28 AM John Naylor
wrote:
> Now that we have a concept of a fail-safe vacuum, maybe it would be
> beneficial to skip a vacuum in single-user mode if the fail-safe
> criteria were not met at the beginning of vacuuming a relation.
Obviously the main goal of the failsafe is
On Thu, Dec 9, 2021 at 1:04 PM Peter Geoghegan wrote:
> On Thu, Dec 9, 2021 at 11:28 AM John Naylor
> wrote:
> > Now that we have a concept of a fail-safe vacuum, maybe it would be
> > beneficial to skip a vacuum in single-user mode if the fail-safe
> > criteria were not met at the beginning of v
On Fri, Dec 10, 2021 at 8:38 AM Andres Freund wrote:
> On 2021-12-09 08:12:14 -0500, Andrew Dunstan wrote:
> > > Does anyone want to object to the concept of the "pg_user_files"
> > > directory or the developer-only GUC "allow_relative_tablespaces"?
> > > There's room for discussion about names; m
Hi,
On 2021-12-09 12:10:23 +1300, Thomas Munro wrote:
> From a60ada37f3ff7d311d56fe453b2abeadf0b350e5 Mon Sep 17 00:00:00 2001
> From: Thomas Munro
> Date: Wed, 4 Aug 2021 22:17:54 +1200
> Subject: [PATCH v8 2/5] Use relative paths for tablespace regression test.
>
> Remove the machinery from pg
Hi,
On 2021-12-09 15:28:18 -0400, John Naylor wrote:
> When a user must shut down and restart in single-user mode to run
> vacuum on an entire database, that does a lot of work that's
> unnecessary for getting the system online again, even without
> index_cleanup. We had a recent case where a sing
I forgot but had actually implemented this 6 months ago.
>From 748da82347f1bfc793ef58de0fa2cb9664e18c52 Mon Sep 17 00:00:00 2001
From: Justin Pryzby
Date: Sun, 7 Mar 2021 19:35:37 -0600
Subject: [PATCH 2/2] Add pg_dump/restore --no-table-am..
This was for some reason omitted from 3b925e905.
---
Hi,
thanks for the reply!
From: Tomas Vondra
Sent: Thursday, December 2, 2021 20:58
Subject: Re: PATCH: generate fractional cheapest paths in
generate_orderedappend_path
> [...]
> Well, I mentioned three open questions in my first message, and I don't
> think we've really addressed them yet. We
On Thu, Dec 9, 2021 at 5:13 PM Peter Geoghegan wrote:
> Oh, I think I misunderstood. Your concern is for the case where the
> DBA runs a simple "VACUUM" in single-user mode; you want to skip over
> tables that don't really need to advance relfrozenxid, automatically.
Right.
> I can see an argume
On Fri, Dec 10, 2021 at 10:36 AM Andres Freund wrote:
> Seems like we ought to add a tiny tap test or such for this - otherwise we
> won't have any coverage of "normal" tablespaces? I don't think they need to be
> exercised as part of the normal tests, but having some very basic testing
> in a tap
On Fri, Dec 10, 2021 at 12:58 PM Thomas Munro wrote:
> +$node_primary->adjust_conf('postgresql.conf', 'max_connections', '25', 1);
Erm, in fact this requirement came about in an earlier version where I
was invoking make and getting --max-concurrent-tests=20 from
src/test/regress/GNUmakefile. Whi
On Thu, Dec 9, 2021 at 3:53 PM John Naylor wrote:
> > single-user mode should prompt the user about
> > what exact VACUUM command they ought to run to get things going.
>
> The current message is particularly bad in its vagueness because some
> users immediately reach for VACUUM FULL, which quite
I just noticed that this (commit 5a2832465fd8) added a separate catalog
to store schemas which are part of a publication, side-by-side with the
catalog to store relations which are part of a publication. This seems
a strange way to represent publication membership: in order to find out
what object
On 12/9/21, 12:33 PM, "Bossart, Nathan" wrote:
> On 12/9/21, 11:34 AM, "John Naylor" wrote:
>> Now that we have a concept of a fail-safe vacuum, maybe it would be
>> beneficial to skip a vacuum in single-user mode if the fail-safe
>> criteria were not met at the beginning of vacuuming a relation.
On 12/9/21, 4:36 PM, "Peter Geoghegan" wrote:
> We could then apply this criteria in new code that implements this
> "big red button" (maybe this is a new option for the postgres
> executable, a little like --single?). Something that's reasonably
> targeted, and dead simple to use.
+1
Nathan
On 12/9/21, 5:06 PM, "Bossart, Nathan" wrote:
> On 12/9/21, 4:36 PM, "Peter Geoghegan" wrote:
>> We could then apply this criteria in new code that implements this
>> "big red button" (maybe this is a new option for the postgres
>> executable, a little like --single?). Something that's reasonably
On Thu, Dec 9, 2021 at 5:12 PM Bossart, Nathan wrote:
> As Andres noted, such a feature might be useful during normal
> operation, too. Perhaps the vacuumdb --min-xid-age stuff should be
> moved to a new VACUUM option.
I was thinking of something like pg_import_system_collations() for
this: a fu
Hi,
On 2021-12-09 16:34:53 -0800, Peter Geoghegan wrote:
> But even still, why not have some variant of single-user mode just for
> this task?
> Something that's easy to use when the DBA is rudely
> awakened at 4am -- something a little bit like a big red button that
> fixes the exact problem of
On Thu, Dec 9, 2021 at 7:23 PM Neha Sharma
wrote:
> On Thu, Dec 9, 2021 at 11:12 AM Ashutosh Sharma
> wrote:
>
>> Hi,
>>
>> The issue here is that we are trying to create a table that exists inside
>> a non-default tablespace when doing ALTER DATABASE. I think this should be
>> skipped otherwise
On Thu, Dec 9, 2021 at 5:56 PM Andres Freund wrote:
> I think we should move *away* from single user mode, rather than the
> opposite. It's a substantial code burden and it's hard to use.
I wouldn't say that this is moving closer to single user mode.
> I don't think single user mode is a good fi
On Fri, Dec 10, 2021 at 6:24 AM Alvaro Herrera wrote:
>
> I just noticed that this (commit 5a2832465fd8) added a separate catalog
> to store schemas which are part of a publication, side-by-side with the
> catalog to store relations which are part of a publication. This seems
> a strange way to r
On Thu, Dec 9, 2021 at 9:16 PM Thomas Munro wrote:
> Slightly improvement: now I include only from
> src/port/open.c and src/port/win32ntdll.c, so I avoid the extra
> include for the other ~1500 translation units. That requires a small
> extra step to work, see comment in win32ntdll.h. I checke
On Thu, Dec 9, 2021 at 10:52 PM Mark Dilger
wrote:
>
> > On Dec 9, 2021, at 7:41 AM, Robert Haas wrote:
> >
> > On Tue, Nov 30, 2021 at 6:55 AM Amit Kapila wrote:
> >>> This patch does detect ownership changes more quickly (at the
> >>> transaction boundary) than the current code (only when it r
On Tue, Jul 6, 2021 at 1:43 PM Michael Paquier wrote:
> This is a large bump for Studio >= 2015 I am afraid. That does not
> seem acceptable, as it means losing support for GetLocaleInfoEx()
> across older versions.
Playing the devil's advocate here: why shouldn't we routinely drop
support for a
On Fri, Dec 10, 2021 at 5:23 PM Thomas Munro wrote:
> Playing the devil's advocate here: why shouldn't we routinely drop
> support for anything that'll be EOL'd when a given PostgreSQL major
> release ships? The current policy seems somewhat extreme in the other
> direction: our target OS baselin
Thomas Munro writes:
> Playing the devil's advocate here: why shouldn't we routinely drop
> support for anything that'll be EOL'd when a given PostgreSQL major
> release ships?
I don't like the word "routinely" here. Your next bit is a better
argument:
> Something EOL'd over a year ago that has
On 12/9/21, 5:27 PM, "Peter Geoghegan" wrote:
> I imagine that this new function (to handle maintenance tasks in the
> event of a wraparound emergency) would output information about its
> progress. For example, it would make an up-front decision about which
> tables needed to be vacuumed in order
Can we change the default setting of track_io_timing to on?
I see a lot of questions, such as over at stackoverflow or
dba.stackexchange.com, where people ask for help with plans that would be
much more useful were this on. Maybe they just don't know better, maybe
they can't turn it on because th
On Thu, Dec 9, 2021 at 6:16 PM Amit Kapila wrote:
>
> On Thu, Dec 9, 2021 at 2:24 PM Masahiko Sawada wrote:
> >
> > On Thu, Dec 9, 2021 at 11:47 AM Amit Kapila wrote:
> > >
> > > I am thinking that we can start a transaction, update the catalog,
> > > commit that transaction. Then start a new on
pg_strtouint64() is a wrapper around strtoull/strtoul/_strtoui64, but it
seems no longer necessary to have this indirection.
msvc/Solution.pm claims HAVE_STRTOULL, so the "MSVC only" part seems
unnecessary. Also, we have code in c.h to substitute alternatives for
strtoull() if not found, and
Dear Fujii-san,
I apologize for sending bad patches...
I confirmed that it can be built and passed a test.
> Could you tell me why you added new paragraph into the middle of existing
> paragraph? This change caused the following error when compiling the docs.
>
> postgres-fdw.sgml:952: parser er
87 matches
Mail list logo
