houldn't be any considerably
large strings here, so the general trend is clear.
Please correct me if I'm wrong.
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
Hi!
On 16.01.2025 04:36, Tom Lane wrote:
"Anton A. Melnikov" writes:
Seems it is possible to exclude much less code from checking
under valgrind and get the same result by replacing the only
function call pg_rightmost_one_pos64() with a valgrind-safe
code. See the attached pat
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres CompanyFrom 7af05703e59fb8f1e51ec1d667ddc150c40756f0 Mon Sep 17 00:00:00 2001
From: "Anton A. Melnikov"
Date: Thu, 16 Jan 2025 02:56:52 +0300
Subject: [PATCH] Add valgrind-
Hi!
On 19.12.2024 06:21, John Naylor wrote:
On Thu, Dec 19, 2024 at 7:10 AM Anton A. Melnikov
wrote:
Found that
https://github.com/postgres/postgres/commit/0aba2554409ee3251d7558567edd114d8ed36dcc
produces a valgrind error in initdb.
What architecture and valgrind version is this? We&#x
GUC? E.g. introduce а max_query_operations GUC
or a variable in such a way that old work_mem will be equal
to max_backend_memory divided by max_query_operations.
What do you think about such approach?
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.co
==00:00:00:01.856 967784==
==00:00:00:01.856 967784== Exit program on first error
(--exit-on-first-error=yes)
child process exited with exit code 1
The current master at b7493e1 also has this error.
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
T
we can try to reproduce similar behavior
in the testing environment and probably detect a hidden bug like in [1].
Thanks a lot for fixing this!
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
[1]
https://www.postgre
is code.
Maybe it's worth adding a warning as well,
similar to the one a few lines below in the code?
Like in the patch attached?
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres CompanyFrom 1becbfa1c873174f7311ad57569a4c
On 03.12.2024 18:07, Andres Freund wrote:
Hi,
On 2024-12-03 13:37:48 +0300, Anton A. Melnikov wrote:
Found a place in the code of this patch that is unclear to me:
https://github.com/postgres/postgres/blob/1acf10549e64c6a52ced570d712fcba1a2f5d1ec/src/backend/utils/activity/pgstat.c#L1658
that such an issue should unlikely be a problem in
practice.
So i doubt whether this should be treated as a bug and to be fixed?
Would be glad to figure this out.
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companysetup
this assert really needed here? And if so, for what?
Would be glad for clarification.
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On 10.10.2024 18:14, Fujii Masao wrote:
Thanks for the review! Pushed.
Thanks a lot!
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
t the patch. Just in case, checked that neither
“backend completed” nor “backend requested” were found anywhere else.
All is ok for me.
Thanks a lot!
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
a error. Thanks!
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
checked v4 with the travis patch-tester. All is ok.
With the best wishes!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
um_performed().
With the best regards!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From 5832b1beb453b96a6ccbe72c404f2ad5373d0497 Mon Sep 17 00:00:00 2001
From: "Anton A. Melnikov"
Date: Thu, 19 Sep 2024 12:51:17 +0300
Subject:
CreateRestartPoint().
And slightly adjusted the patch so that it could be applied after yours.
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres CompanyFrom 97595f65cb12eb2243e1b7391e1bc77bd161f41c Mon Sep 17 00:00:00 2001
From: "An
frequently (13 seconds apart)
2024-09-16 16:38:47.888 MSK [193733] HINT: Consider increasing the configuration
parameter "max_wal_size".
And num_timed + num_requested will become greater than num_done.
Would be nice to find some simpler and faster way.
With the best regards,
--
patch that tries to do this based on the your first patch.
Would be glad to hear your opinion.
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres CompanyFrom 4b6a12f6eaac98ee22dd63d64431968357905d77 Mon Sep 17 00:00:00 2001
From: &qu
On 04.09.2024 23:26, Tom Lane wrote:
Pushed. I shall now watch the buildfarm from a safe distance.
Thanks! I'll be ready to fix possible falls.
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
ace for this?
In v2 moved some definitions from xlog_internal to xlogdefs
and removed including xlog_internal.h from the postmaster.c.
Please, take a look on it.
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres CompanyFrom 0b1435492e293ee5553a69c
ve this problem only from the knn-btree patch side.
Could you advise any ways how to deal with this. Would be very grateful.
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
[1]
https://commitfest.postgres
elcome.
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
the last couple years.
Agreed that no reason to save workarounds for non-supported systems.
Here is the patch that removes fixes for Buster bug mentioned above.
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postg
On 14.06.2024 10:45, Anton A. Melnikov wrote:
The src/backend/access/heap/README.tuplock says about HEAP_XMAX_INVALID bit
that "Any tuple with this bit set does not have a valid value stored in XMAX."
Found that FreezeMultiXactId() tries to process such an invalid multi xmax
and may
true;
+ return InvalidTransactionId;
+ }
+
if (!MultiXactIdIsValid(multi) ||
HEAP_LOCKED_UPGRADED(t_infomask))
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
10,
then it makes sense to look for more complex solutions that will fix a
backslash substitutions.
If no such complaints, then it is better to make a workaround in test.
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
like [1].
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
[1] https://www.postgresql.org/message-id/960764.1643751...@sss.pgh.pa.usFrom 455bec0d785b0f5057fc7e91a5fede458cf8fd36 Mon Sep 17 00:00:00 2001
From: "Anto
On 28.04.2024 22:36, Heikki Linnakangas wrote:
Peter E noticed and Michael fixed them in commit 768ceeeaa1 already.
Didn't check that is already fixed in the current master. Sorry!
Thanks for pointing this out!
With the best wishes,
--
Anton A. Melnikov
Postgres Professional:
Hello!
Maybe add PGDLLIMPORT to
extern bool LoadedSSL;
and
extern struct ClientSocket *MyClientSocket;
definitions in the src/include/postmaster/postmaster.h ?
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On 24.04.2024 12:19, Daniel Gustafsson wrote:
On 24 Apr 2024, at 11:13, Anton A. Melnikov wrote:
On 24.04.2024 12:02, Peter Eisentraut wrote:
On 19.04.24 05:50, Anton A. Melnikov wrote:
May be better use this macro everywhere in C code?
I don't know. I don't find XLOG_CONTROL_FI
On 24.04.2024 12:02, Peter Eisentraut wrote:
On 19.04.24 05:50, Anton A. Melnikov wrote:
May be better use this macro everywhere in C code?
I don't know. I don't find XLOG_CONTROL_FILE to be a very intuitive proxy for
"pg_control".
Then maybe replace XL
On 20.04.2024 09:36, Daniel Gustafsson wrote:
Anton: please register this patch in the Open commitfest to ensure it's not
forgotten about.
Done.
Daniel and Michael thank you!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
this.
Would be glad if take a look on it.
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres CompanyFrom 2692683142c98572114c32f696b55c6a642dd3e9 Mon Sep 17 00:00:00 2001
From: "Anton A. Melnikov"
Date: Fri, 19 Apr 2024 06:1
too.
Additional check for relminxid allows to disable agressive scan
at all if it is invalid. But i'm not sure if such a check is needed here.
Please take it into account.
With kindly regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companyc
Hi, Andrey!
On 31.03.2024 12:22, Andrey M. Borodin wrote:
On 15 Jan 2024, at 13:11, Anton A. Melnikov wrote:
If there are any ideas pro and contra would be glad to discuss them.
Hi, Anton!
This is kind of ancient thread. I've marked CF entry [0] as "Needs review" and
y
On 22.03.2024 11:02, Pavel Borisov wrote:
Attached is a fix.
Thanks!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
ot; in the last arg does not match the previous code before
06b10f80ba
and the current comment above.
Would be very grateful for clarification.
With the best regards!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On 13.03.2024 10:41, Anton A. Melnikov wrote:
Here is a version updated for the current master.
During patch updating i mistakenly added double counting of deallocatated
blocks.
That's why the tests in the patch tester failed.
Fixed it and squashed fix 0002 with 0001.
Here is fixed ve
On 14.03.2024 03:19, Alexander Korotkov wrote:
Pushed.
Thanks!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On 12.03.2024 16:30, Aleksander Alekseev wrote:
Just wanted to let you know that v20231226 doesn't apply. The patch
needs love from somebody interested in it.
Thanks for pointing to this!
Here is a version updated for the current master.
With the best regards,
--
Anton A. Melnikov
Pos
took a fresh look at this patch i noticed a simple way to extract
write_time and sync_time counters for restartpoints too.
What do you think, is there a sense to do this?
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On 16.01.2024 14:54, Heikki Linnakangas wrote:
Fixed, thanks. mark_pgdllimport.pl also highlighted two new variables in
walsummarizer.h, fixed those too.
Thanks!
Have a nice day!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On 25.12.2023 02:38, Alexander Korotkov wrote:
Pushed!
Thanks a lot!
With the best regards!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
e glad for any comments and and concerns.
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companycommit 5711c09dbfbe02586a247a98e0ae41cd71a221a3
Author: Anton A. Melnikov
Date: Sun Dec 3 12:49:11 2023 +0300
GRANT) are not copied from the template
database.
Clear. Thank you very much!
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
please. Is this normal, predictable behavior?
Would be very grateful!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
. Probably something wrong with my pc, but
now
i can not figure out what's wrong.
Would be very grateful for any advice or comments to clarify this problem.
With the best wishes!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
REL_10_STABL
On 02.11.2023 01:53, Michael Paquier wrote:> On Thu, Nov 02, 2023 at 12:28:05AM
+0300, Anton A. Melnikov wrote:
Found that src/test/modules/test_misc/t/003_check_guc.pl will crash if an
extension
that adds own GUCs was loaded into memory.
So it is now impossible to run a check-world w
LE' = ANY (pg_settings_get_flags(name)) AND
- name <> 'config_file'
+ name <> 'config_file' AND name NOT LIKE '%.%'
ORDER BY 1");
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Ru
[]
(1 row)
And at the moment i havn't found any side effects of that fix.
Please point me if i'm missing something.
With the best wishes!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
7;)
);
INSERT INTO test_jsonb_constraints VALUES ('[]');
one expected to see an error like that:
ERROR: new row for relation "test" violates check constraint "test_constraint"
DETAIL: Failing row contains ([], null, [1, 2]).
not "INSERT 0 1"
With
n.
Thanks for your interest!
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
.
How do you think, is there any cause for concern here?
And is it worth spending time bisecting for the commit where this degradation
may have occurred?
Would be glad for any comments and concerns.
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The
Sorry, attached the wrong version of the file. Here is the right one.
Sincerely yours,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
alg_level_up.pdf
Description: Adobe PDF document
earlier than August 2 evening]
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
alg_level_up.pdf
Description: Adobe PDF document
On 25.07.2023 06:24, Andres Freund wrote:
Thanks Anton / Victoria for the report and fix. Pushed.
Thanks!
Have a nice day!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
e.g. if shared_buffers = 10MB and
max_worker_processes = 40.
Then the command "pgbench --initialize postgres" will lead to crash.
See the backtrace attached.
There is a fix in the patch applied. Please take a look on it.
With the best regards,
--
Anton A. Melnikov
Postgres Professi
y varnos during custom_scan->scan.plan.targetlist creation and leave the
сustom_scan->custom_scan_tlist = NIL rather than changing them later using
ChangeVarNodes().
This resulted in a noticeable code simplification.
Thanks a lot for pointing on it!
Sincerely yours,
--
Anton A. Melnikov
Postgr
ds,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companycommit cc1724759b898efc703867a83d38173e4b2794b5
Author: Anton A. Melnikov
Date: Mon May 29 13:52:42 2023 +0300
Return false from bms_is_member() if checked value is negative.
diff --git a/sr
context->rt_index >= 0 && context->new_index >= 0)
+ var->varnullingrels =
adjust_relid_set(var->varnullingrels,
+
context->rt_index,
+
With the best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On 05.04.2023 17:35, Tom Lane wrote:
"Anton A. Melnikov" writes:
On 03.04.2023 21:49, Tom Lane wrote:
I did not think this case was worth memorializing in a test before,
and I still do not. I'm inclined to reject this patch.
Could you help me to figure out, please.
The
Hello!
On 03.04.2023 21:49, Tom Lane wrote:
"Anton A. Melnikov" writes:
Now there are no any pending questions, so moved it to RFC.
I did not think this case was worth memorializing in a test before,
and I still do not. I'm inclined to reject this patch.
Earlier, when
with "my" variable $result and suggestion to correct comment (by
vignesh C)
Both fixed in v4.
Now there are no any pending questions, so moved it to RFC.
With the best regards!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companycommit 16beb57
e it easier for a committer
to understand the state
There are two different patch variants and some discussion expected.
So moved them to the next CF.
With the best wishes!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companycommit 6f3ab7b6b5562aaf68ccfdd6dd
yours,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
ly,
that'd be just like the way we use FPI for data pages copied during a
backup. I'm not sure about any of that, though, it's just an idea,
not tested.
Sorry, i didn't understand the question about log. Would you explain me
please what kind of log did you mention and wher
600/
[2] https://github.com/ut-osa/txfs
[3] https://en.wikipedia.org/wiki/Transactional_NTFS[4]
https://www.postgresql.org/docs/devel/wal-internals.html
With the best wishes!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
Hi, Thomas!
On 14.02.2023 06:38, Anton A. Melnikov wrote:
Also i did several experiments with fsync=on and found more appropriate
behavior:
The stress test with sizeof(ControlFileData) = 512+8 = 520 bytes failed in a
4,5 hours,
but the other one with ordinary sizeof(ControlFileData) = 296 not
arify it for me, please? If
the performance
of UpdateMinRecoveryPoint() wasn't a problem we could just use fsync in all
platforms.
Sincerely yours,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
error
will occur there, then we might use the workaround from the first
variant of the patch.
A thought in passing: if UpdateMinRecoveryPoint() performance is an
issue, maybe we should figure out how to use fdatasync() instead of
fsync().
May be choose it in accordance with GUC wal_sync_method?
es:
xlog.c:2507:1: warning: no previous prototype for ‘pg_update_control_file’
[-Wmissing-prototypes]
2507 | pg_update_control_file()
Fixed it with #include "utils/fmgrprotos.h" to xlog.c and
add PG_FUNCTION_ARGS to pg_update_control_file().
With the best wishes,
--
Anton A. Melnikov
tter message:
+# This would crash on the subscriber if not fixed
+$node_publisher->safe_psql('postgres', "INSERT INTO tab1 VALUES (3, 4)");
+
+my $result = $node_subscriber->wait_for_log(
+ "ERROR: relation \"error_name\" does not exis
On 27.12.2022 16:50, Michael Paquier wrote:
If there are no other considerations could you close the corresponding
record on the January CF, please?
Indeed, now marked as committed.
-
Thanks a lot!
Merry Christmas!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The
in the external files.
I would like to try realize this, better in a separate thread.
If there are no other considerations could you close the corresponding
record on the January CF, please?
With the best wishes!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
Hello!
On 23.12.2022 05:42, Michael Paquier wrote:
On Thu, Dec 22, 2022 at 09:59:18AM +0300, Anton A. Melnikov wrote:
2) v2-0002-Additional-dumps-filtering.patch
+ # Replace specific privilegies with ALL
+ $dump_contents =~ s/^(GRANT\s|REVOKE\s)(\S*)\s/$1ALL /mgx;
This should not
oid
AND a.atttypid = 'aclitem'::regtype
ORDER BY 1
LOOP
EXECUTE 'ALTER TABLE ' || quote_ident(rec.rel) || ' ALTER COLUMN ' ||
quote_ident(rec.col) || ' SET DATA TYPE text';
END LOOP;
END; $$;
gives the average time of 36 ms at t
;
END LOOP;
END;
$$;
Average execution time for three times:
_
|N of query: | 1 | 2 | 3 | 4 |
|
|Avg time, ms: | 58 | 1076 | 51 | 33 |
|
Raw results in timing.txt
Best wishes,
--
An
upgrade.pl a small-ish hook
in the shape of a new environment variable pointing to a file adds
some custom filtering rules?
Yes. Made a hook that allows to proceed an external text file with additional
filtering rules and example of such file. Please take a look o
Hello!
On 09.12.2022 08:19, Michael Paquier wrote:
On Mon, Aug 01, 2022 at 01:02:21AM +0300, Anton A. Melnikov wrote:
As far as i understand from this thread:
https://www.postgresql.org/message-id/flat/Yox1ME99GhAemMq1%40paquier.xyz,
the aim of the perl version for the pg_upgrade tests is to
is, i propose to replace any specific GRANT and REVOKE in the result
dumps with ALL.
This also made in the patch attached.
Would be glad to any remarks.
With best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companycommit e2c917694acc7
eund
Thank you for reminding!
There was a conflict when applying v2 on current master.
Rebased v3 is attached.
Best wishes!
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companycommit 07eaa674953ed700a53174410a6e1eb81151d7e8
Author: Anton A. Melnikov
D
Hello!
On 06.12.2022 21:44, Andres Freund wrote:
Hi,
On 2022-09-19 01:29:21 +0300, Anton A. Melnikov wrote:
Corrected patch is attached (v2-0001-Fix-burst-checkpoint_req-growth.patch).
This patch doesn't pass the main regression tests tests successfully:
https://cirrus-ci.com
On 25.11.2022 10:34, Michael Paquier wrote:
On Fri, Nov 25, 2022 at 10:13:29AM +0300, Anton A. Melnikov wrote:
The test fails almost at the beginning in reset_pg_hba call after
modification pg_hba.conf and node reloading:
#t/003_peer.pl .. Dubious, test returned 2 (wstat 512, 0x200)
#No
d.
With best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company2022-11-25 09:55:49.731 MSK [7648] LOG: starting PostgreSQL 16devel, compiled by Visual C++ build 1929, 64-bit
2022-11-25 09:55:49.735 MSK [7648] LOG: listening on IPv4 addre
x27;
May be disable this test for windows like in 001_password.pl and
002_saslprep.pl?
Best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companycommit e4491b91729b307d29ce0205b455936b3a538373
Author: Anton A. Melnikov
Date: Fri Nov 25 07:40:11
buildfarm
animals are going to run the tests in the future.
On 15.11.2022 04:59, Tom Lane wrote:
"Anton A. Melnikov" writes:
On 02.11.2022 21:02, Tom Lane wrote:
I don't think the cost of that test case is justified by the tiny
probability that it'd ever catch anyt
Hello!
The previous discussion was here:
https://www.postgresql.org/message-id/flat/b570c367-ba38-95f3-f62d-5f59b9808226%40inbox.ru
On 15.11.2022 04:59, Tom Lane wrote:
"Anton A. Melnikov" writes:
Additionally
i've tried to reduce overall number of nodes previously
used in
en checking for specific error messages.
Seems it is possible to do a test without these remarks. The attached
test uses existing nodes and checks the specific error message. Additionally
i've tried to reduce overall number of nodes previously
used in this test in a similar way.
Would be
With best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companydiff --git a/src/bin/pg_upgrade/.gitignore b/src/bin/pg_upgrade/.gitignore
index 2d3bfeaa50..05200a09f1 100644
--- a/src/bin/pg_upgrade/.gitignore
+++ b/src/bin/pg_upgrade/.gitignore
@
server just deal with it. It works
because the system needs to do those kinds of things anyway so, why not make it
user-facing, even if most uses would find its restrictions makes it undesirable
to use.
David J.
All the best,
--
Anton A. Melnikov
Postgres Professional: http
ol with
ERROR: cannot insert multiple commands into a prepared statement.
What are their advantages?
And what is the proper name for such queries? "Compound" or something else?
Would be very grateful for clarification.
Best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
t a warning but a notice
message
before OldestXmin WARNING and possible real problems in the future.
Maybe it can be useful in a such kind?
With best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
hed tries to do this.
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companycommit f27ea4e61a7680452b56a7c11b1dcab1c0b81c6b
Author: Anton A. Melnikov
Date: Fri Oct 14 11:57:22 2022 +0300
Split 'too far in the past checks' in vacuum_set_x
ttached patch does it.
Best wishes,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companycommit bfaa02ac7a7cbeb793747be71962a7799c60c21c
Author: Anton A. Melnikov
Date: Sun Oct 9 11:56:20 2022 +0300
Fix logical replica crash if there was an error in
q | 109
With best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companycommit d5a58d8585692be0d24db9414859088e3e7f7dad
Author: Anton A. Melnikov
Date: Tue Sep 6 12:18:56 2022 +0300
Remove burst growth of the checkpoint_req on re
Hello!
Added a TAP test for this case.
On 30.08.2022 10:09, Anton A. Melnikov wrote:
Hello!
The patch was rebased on current master.
And here is a simplified crash reproduction:
1) On primary with 'wal_level = logical' execute:
CREATE TABLE public.test (id int NOT NULL, v
ies to fix it.
With best regards.
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company022-09-04 21:09:45.160 MSK [2424110] LOG: Start CFS version 0.54 supported compression algorithms pglz,zlib encryption disabled GC enabled
2022-09-04 21:09:45.1
repcmd.sql attached with primary port and
execute it:
psql -f repcmd.sql
3) On master execute command:
INSERT INTO test VALUES ('1');
With best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companycommit 4de66e1b1ffaeaacdd72f3e7278
1 - 100 of 119 matches
Mail list logo
