From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
---|---|
To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Shubham Barai <shubhambaraiss(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Borodin <amborodin86(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com> |
Subject: | Re: [HACKERS] GSoC 2017: weekly progress reports (week 6) |
Date: | 2018-04-09 11:43:41 |
Message-ID: | 190cd793-cb1c-e40d-fb78-605d565f2b3e@sigaev.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
Ugh, I miss your last email where you another locking protocol. Reading.
Teodor Sigaev wrote:
>> Attached is a test case that demonstrates a case where we miss a serialization
>> failure, when fastupdate is turned on concurrently. It works on v10, but fails
>> to throw a serialization error on v11.
> Thank you for reserching!
>
> Proof of concept:
> diff --git a/src/backend/commands/tablecmds.c b/src/backend/commands/tablecmds.c
> index 43b2fce2c5..b8291f96e2 100644
> --- a/src/backend/commands/tablecmds.c
> +++ b/src/backend/commands/tablecmds.c
> @@ -10745,6 +10745,7 @@ ATExecSetRelOptions(Relation rel, List *defList,
> AlterTableType operation,
> case RELKIND_INDEX:
> case RELKIND_PARTITIONED_INDEX:
> (void) index_reloptions(rel->rd_amroutine->amoptions, newOptions,
> true);
> + TransferPredicateLocksToHeapRelation(rel);
> break;
> default:
> ereport(ERROR,
>
> it fixes pointed bug, but will gives false positives. Right place for that in
> ginoptions function, but ginoptions doesn't has an access to relation structure
> and I don't see a reason why it should.
>
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
From | Date | Subject | |
---|---|---|---|
Next Message | Geoff Winkless | 2018-04-09 12:03:28 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |
Previous Message | Rushabh Lathia | 2018-04-09 11:42:41 | Re: Commit 4dba331cb3 broke ATTACH PARTITION behaviour. |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-04-09 12:59:17 | Re: Edit access to PostgreSQL Ecosystem Wiki Page |
Previous Message | Teodor Sigaev | 2018-04-09 11:35:05 | Re: [HACKERS] GSoC 2017: weekly progress reports (week 6) |