Re: Re: Burst in WAL size when UUID is used as PK while full_page_writes are enabled

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Thomas Kellerer <spam_eater(at)gmx(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: Burst in WAL size when UUID is used as PK while full_page_writes are enabled
Date: 2017-10-27 13:21:40
Message-ID: CAA4eK1JrkR_nuquVf44hfVou06MBe9bWWq0ZN4Uc=wCDVCjxMw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 27, 2017 at 5:46 PM, Thomas Kellerer <spam_eater(at)gmx(dot)net> wrote:
> akapila wrote:
>
>> You might want to give a try with the hash index if you are planning
>> to use PG10 and your queries involve equality operations.
>
> But you can't replace the PK index with a hash index, because hash indexes
> don't support uniqueness.
>

That's true, but it hasn't been mentioned in the mail that the usage
of hash index is the for primary key.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-10-27 13:24:12 Re: MERGE SQL Statement for PG11
Previous Message Amit Kapila 2017-10-27 13:19:01 Re: Burst in WAL size when UUID is used as PK while full_page_writes are enabled