Re: BUG #17986: Inconsistent results of SELECT affected by btree index

Поиск
Список
Период
Сортировка
От Tomas Vondra
Тема Re: BUG #17986: Inconsistent results of SELECT affected by btree index
Дата
Msg-id e73bf331-7b1d-9808-d909-80688e318a88@enterprisedb.com
обсуждение исходный текст
Ответ на BUG #17986: Inconsistent results of SELECT affected by btree index  (PG Bug reporting form <noreply@postgresql.org>)
Ответы Re: BUG #17986: Inconsistent results of SELECT affected by btree index  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs

On 6/20/23 22:54, PG Bug reporting form wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      17986
> Logged by:          Zuming Jiang
> Email address:      zuming.jiang@inf.ethz.ch
> PostgreSQL version: 16beta1
> Operating system:   Ubuntu 20.04
> Description:        
> 
> My fuzzer finds a correctness bug in Postgres, which makes Postgres return
> inconsistent results. This bug can be reproduced even after applying the
> fixing patches for 
> https://www.postgresql.org/message-id/flat/17976-4b638b525e9a983b%40postgresql.org
> 
> https://www.postgresql.org/message-id/flat/17982-3fa239feecd6c1b3%40postgresql.org
> https://www.postgresql.org/message-id/flat/17985-748b66607acd432e%40postgresql.org
> 
> ...
> 
> --- Postgres version ---
> Github commit: efeb12ef0bfef0b5aa966a56bb4dbb1f936bda0c
> Version: PostgreSQL 16beta1 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu
> 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit
> 

I can't reproduce this with current master - perhaps one of the commits
since efeb12ef0b fixes this too? Those should be for the patches you
mentioned, but it's likely a bit improved.

Can you try with current master?


regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



В списке pgsql-bugs по дате отправления:

Предыдущее
От: Thomas Munro
Дата:
Сообщение: Re: BUG #17949: Adding an index introduces serialisation anomalies.
Следующее
От: Japin Li
Дата:
Сообщение: Re: BUG #17983: Assert IsTransactionState() failed when empty string statement prepared in aborted transaction