Ok you mean that xid64 will remove the need for freezing... it's a way to
see things.
Le mar. 18 févr. 2025 à 15:57, Greg Sabino Mullane a
écrit :
> On Tue, Feb 18, 2025 at 9:17 AM Sébastien wrote:
>
>> Sorry it won't work. It just delays the problem. But still the fr
Sorry it won't work. It just delays the problem. But still the freeze
procedure must rewrite all pages.
Le mar. 18 févr. 2025, 04:12, wenhui qiu a écrit :
> Hello Sébastien
> this case can be solved by xid64,but it seems like very few people
> are interested.But it seems to
> HI Sébastien
> You can check out the email subject:Trigger more frequent autovacuums
> of heavy insert tables , I think it can alleviate the problem
>
> Thanks
>
> On Sat, Feb 15, 2025 at 3:13 AM Andres Freund wrote:
>
>> Hi,
>>
>> On 2025-02-13 10:
e is that if the
> transaction rolls back, the table will never have been visible to any
> other transaction at all, so that maintaining atomicity/integrity of
> its contents is moot.
>
> regards, tom lane
>
> [1]
> https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=052026c9b
>
--
Sébastien Caunes
+33 6 7 229 229 7
#x27;s not that much and pretty straightforward to implement
experimentally. Then.
Opportunity Window Period:
...
Budget Money:
...
Contact Information:
If you have further question regarding the issues I experienced that this
would solve, feel free to contact me
Sébastien Caunes bokan...@gmail.com
Introduce per-database transaction logs (WAL) and transaction ID spaces to
improve database isolation, enable hot-mounting/unmounting, selective
replication, and open new possibilities in PostgreSQL.
Business Use-case:
With modern SSDs offering high throughput and low latency, maintaining a
single
ou for the patch ; I've tried it and it works with the scenario
you provide.
As Nicolas's co-worker, I've been involved in this case, but,
unfortunately, we're not able to test the patch with the actual data for
the moment, but I'll ask a dump to the real owner.
About the regression test, I don't know how to implement it either.
best regards,
--
Sébastien
On 21/03/2023 08:15, Peter Eisentraut wrote:
On 20.03.23 10:40, Sébastien Lardière wrote:
About option_parse_int(), actually, strtoint() is used, do we need
a option_parse_ul() fonction ?
For the option parsing, I propose the attached patch. This follows
the structure of option_parse_int
On 20/03/2023 09:17, Peter Eisentraut wrote:
I have committed the two documentation changes, with some minor
adjustments.
Thank you,
On 07.03.23 18:14, Sébastien Lardière wrote:
Maybe this could be fixed instead?
Indeed, and strtoul is probably a better option than sscanf, don't
On 06/03/2023 18:04, Peter Eisentraut wrote:
On 03.03.23 16:52, Sébastien Lardière wrote:
On 02/03/2023 09:12, Peter Eisentraut wrote:
I think here it would be more helpful to show actual examples. Like,
here is a possible file name, this is what the different parts mean.
So you mean
On 02/03/2023 09:12, Peter Eisentraut wrote:
On 24.02.23 17:27, Sébastien Lardière wrote:
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index be05a33205..7e26b51031 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1332,7 +1332,8 @@ restore_command
On 31/01/2023 20:16, Greg Stark wrote:
A hint or something just in
that case might be enough?
It seems to be a -1 ;
let's try to improve the documentation, with the attached patch
best regards,
--
Sébastien
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index be05a
l in filenames but must be
used in decimal in recovery_target_timeline and pg_waldump ?
regards,
--
Sébastien
On 31/01/2023 10:53, Peter Eisentraut wrote:
On 30.01.23 17:05, Sébastien Lardière wrote:
Here's the patch with the suggested format ; plus, I add some note in
the documentation about recovery_target_timeline, because I don't get
how strtoul(), with the special 0 base paramete
On 31/01/2023 12:26, Ashutosh Bapat wrote:
On Mon, Jan 30, 2023 at 9:35 PM Sébastien Lardière
wrote:
On 27/01/2023 15:55, Peter Eisentraut wrote:
On 27.01.23 14:52, Sébastien Lardière wrote:
The attached patch proposes to change the format of timelineid from
%u to %X.
I think your complaint
On 27/01/2023 15:55, Peter Eisentraut wrote:
On 27.01.23 14:52, Sébastien Lardière wrote:
The attached patch proposes to change the format of timelineid from
%u to %X.
I think your complaint has merit. But note that if we did a change
like this, then log files or reports from different
On 27/01/2023 15:55, Peter Eisentraut wrote:
On 27.01.23 14:52, Sébastien Lardière wrote:
The attached patch proposes to change the format of timelineid from
%u to %X.
I think your complaint has merit. But note that if we did a change
like this, then log files or reports from different
ch proposes to change the format of timelineid from %u
to %X.
Regarding .po files, I don't know how to manage them. Is there any
routine to spread the modifications? Or should I identify and change
each message?
best regards,
--
Sébastien
diff --git a/src/backend/access/rmgrdesc/xlogdesc.c
;t be /help ?
Same thing in the release note
(https://www.postgresql.org/docs/13/release-13.html) :
> Add the PostgreSQL home page to command-line |--help| output (Peter
Eisentraut)
as it probalbly refer to 27f3dea64833d68c1fa08c1e5d26176a579f69c8, isn't
it ?
regards,
--
Sébastien
19 matches
Mail list logo
