From: Aleksander Alekseev <a.alekseev@postgrespro.ru>
To: Anastasia Lubennikova <a.lubennikova@postgrespro.ru>
Cc: pgsql-hackers@postgresql.org, Thom Brown <thom@linux.com>
Subject: Re: [WIP] Effective storage of duplicates in B-tree index.
Date: Fri, 29 Jan 2016 18:47:33 +0300
Message-ID: <20160129184733.2ca9026a@fujitsu> (raw)
In-Reply-To: <56AB6D30.2040900@postgrespro.ru>
References: <55E4051B.7020209@postgrespro.ru>
<56AA2081.1080001@postgrespro.ru>
<CAA-aLv68Ptrnk2HpHSg9wYR0c+D2AyTB+XrS671brxqQz3dH3w@mail.gmail.com>
<56AA3E06.8040006@postgrespro.ru>
<CAA-aLv5aQezrfh2iJD97R1sQ6nqMsR2QZ_YAzNfAOkkMgO8CFQ@mail.gmail.com>
<56AB6D30.2040900@postgrespro.ru>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
I tested this patch on x64 and ARM servers for a few hours today. The
only problem I could find is that INSERT works considerably slower after
applying a patch. Beside that everything looks fine - no crashes, tests
pass, memory doesn't seem to leak, etc.
> Okay, now for some badness. I've restored a database containing 2
> tables, one 318MB, another 24kB. The 318MB table contains 5 million
> rows with a sequential id column. I get a problem if I try to delete
> many rows from it:
> # delete from contacts where id % 3 != 0 ;
> WARNING: out of shared memory
> WARNING: out of shared memory
> WARNING: out of shared memory
I didn't manage to reproduce this. Thom, could you describe exact steps
to reproduce this issue please?
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: a.alekseev@postgrespro.ru, a.lubennikova@postgrespro.ru, thom@linux.com
Subject: Re: [WIP] Effective storage of duplicates in B-tree index.
In-Reply-To: <20160129184733.2ca9026a@fujitsu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox