nd point 1 addressed, the fix seems to look okay in
RangeVarCallbackForDropRelation.
Thanks for the feedback. Attached new patch with feedback addressed.
--
Jimmy Yih (VMware)
Gaurab Dey (VMware)
v2-0001-Fix-concurrent-deadlock-scenario-with-DROP-INDEX-.patch
Description: v2-0001-Fix-concurrent-deadlock-scenario-with-DROP-INDEX-.patch
th feedback addressed.
--
Jimmy Yih (VMware)
Gaurab Dey (VMware)
v3-0001-Fix-concurrent-deadlock-scenario-with-DROP-INDEX-.patch
Description: v3-0001-Fix-concurrent-deadlock-scenario-with-DROP-INDEX-.patch
a test case that does
> deadlock with unpatched code.
The proposed patches look great and make much more sense. I see you've
already squashed and committed in
7b6ec86532c2ca585d671239bba867fe380448ed. Thanks!
--
Jimmy Yih (VMware)
Gaurab Dey (VMware)
e their Postgres without knowing they were
going to enable WAL archiving later on. The user would need to
configure archiving and force a failover which may not be
straightforward.
Regards,
Jimmy Yih
v2-0001-Archive-current-timeline-history-file-after-recovery.patch
Description: v2-0001-Ar
ition tables beneath the partitioned
index's partitioned table before attempting to lock the sub-partition
and partition indexes.
Attached is a patch (+isolation test) which fixes the issue. We
observed this on latest head of Postgres.
Regards,
Jimmy Yih and Gaurab Dey
0001-Fix-concurren
ily fixed if we determine that the
recovery_target_timeline numeric value is equal to the control file's timeline
id (compare rtli and recoveryTargetTLI in validateRecoveryParameters()?) but I
wasn't sure if maybe the opposite was true where we should make 'current' and
'lates
to archive the current timeline history file if it
has not been archived yet when the archiver process starts up.
Regards,
Jimmy Yih
From: Jimmy Yih
Sent: Wednesday, August 9, 2023 5:00 PM
To: pgsql-hack...@postgresql.org
Subject: Should the archiver
Big congrats to you two!!!
- Jimmy
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidenti
Hello,
In Postgres 8.3, it was decided that an array type would be automatically
created for every heap relation's composite type.
Reference thread:
https://www.postgresql.org/message-id/flat/20070302234016.GF3665%40fetter.org
The possible issue I would like to note is related to how the array t
Hello,
When an empty namespace is being initially populated with certain objects,
it is possible for a DROP SCHEMA operation to come in and delete the
namespace without using CASCADE. These objects would be created but are
left unusable. This is capable of leaving behind pg_class, pg_type, and
o
>
> Something which would be good to have for all those queries is a set of
> isolation tests. No need for multiple specs, you could just use one
> spec with one session defining all the object types you would like to
> work on. How did you find this object list? Did you test all the
> objects a
pg_get_viewdef('fooview');
pg_get_viewdef
SELECT t.a
FROM ( SELECT 1 AS a,
'foo'::text AS baz
UNION
SELECT 0 AS a,
'bar'::text AS baz) t;
(1 row)
Nested subqueries also work with the patch. We're not sure how this could
break.
Is this an acceptable change that should be pursued?
Regards,
Jimmy Yih and Jim Doty
view_union_subquery_constant.patch
Description: Binary data
12 matches
Mail list logo
