Re: Bug in DefineRange() with multiranges

From:	Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru>
To:	Michael Paquier <michael(at)paquier(dot)xyz>
Cc:	Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alex Kozhemyakin <a(dot)kozhemyakin(at)postgrespro(dot)ru>
Subject:	Re: Bug in DefineRange() with multiranges
Date:	2021-10-13 08:35:34
Message-ID:	56914d63-b31b-ac9a-1921-0cac1eddd923@postgrespro.ru
Views:	Raw Message | Whole Thread | Download mbox | Resend email
Thread:	2021-10-04 17:09:28 from Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru>  2021-10-10 17:12:30 from Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>   2021-10-12 05:52:29 from Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru> 📎    2021-10-13 04:21:05 from Michael Paquier <michael(at)paquier(dot)xyz>     2021-10-13 08:35:34 from Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru>
Lists:	pgsql-hackers

In response to

• Re: Bug in DefineRange() with multiranges at 2021-10-13 04:21:05 from Michael Paquier

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Stephen Frost	2021-10-13 08:48:51	Re: should we allow users with a predefined role to access pg_backend_memory_contexts view and pg_log_backend_memory_contexts function?gr
Previous Message	Dilip Kumar	2021-10-13 08:29:51	Re: BUG #17220: ALTER INDEX ALTER COLUMN SET (..) with an optionless opclass makes index and table unusable