, should
we skip any parallel safty check about target relation and build parallel query
plan directly ?
could anyone give me some suggestion about this confusions.
Best Regards
Tomas Ji
| |
jiye
|
|
jiye...@126.com
|
combo cid mapping,
and only other workers can not learn about that, so why those workers must know
leader's combo cids? why those worker
need see leader's updated tuples, could you give me some example cases or
Unusual scenes for for this parallel update?
| |
jiye
|
|
jiye...@126.com
|
down or does
not work.
| |
jiye
|
|
jiye...@126.com
|
Replied Message
| From | Julien Rouhaud |
| Date | 6/7/2023 15:36 |
| To | jiye |
| Cc | robertmh...@gmail.com ,
t...@sss.pgh.pa.us ,
pgsql-hackers@lists.postgresql.org |
| Subject | Re: confusion about this commit "Revert
actually out test instance include 2aa6e331ead7f3ad080561495ad4bd3bc7cd8913
this commit, not yet reverted this commit.
| |
jiye
|
|
jiye...@126.com
|
Replied Message
| From | Julien Rouhaud |
| Date | 6/7/2023 14:00 |
| To | Robert Haas |
| Cc | jiye ,
t...@sss.pgh.pa.us ,
pgsql
down", this lock down implict that
autovacuum can make a dead lock problem ?
3. how to reproduce this lock down or autovacuum invalid issue, must be cluster
enviroment ?
so is there any body know these issuse or commits can give me some suggestion
about my confusion.
| |
jiye
|
|
jiye...@126.com
|
:05:01, "hubert depesz lubaczewski" wrote:
>On Tue, Oct 11, 2022 at 05:43:03PM +0800, jiye wrote:
>> As we know postgres using high level lock when do alter table or other ddl
>> commands,
>> It will block any dml operation, while it also will block by long
Hi,
As we know postgres using high level lock when do alter table or other ddl
commands,
It will block any dml operation, while it also will block by long term dml
operation.
Like what discuss as follow :
