pg.ddx.io pgsql-performance@postgresql.org mailing list archive help / color / mirror / Atom feed From: Andrea Suisani <sickpig@opinioni.net>
To: Tobias Brox <tobixen@gmail.com>
Cc: Vitalii Tymchyshyn <tivv00@gmail.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org, Mladen Gogala <mladen.gogala@vmsinfo.com>
Subject: Re: Why we don't want hints Was: Slow count(*) again...
Date: Fri, 11 Feb 2011 12:33:22 +0100
Message-ID: <4D551E82.7030300@opinioni.net> (raw )
In-Reply-To: <AANLkTikwHQO2TVBYu81CLsBPjcyin3xrK+o7r=WrJ3g7@mail.gmail.com >
References: <201102012247.p11Ml6u02682@momjian.us >
<4D48914B.4050403@dunslane.net >
<4D489AD1.1010105@vmsinfo.com >
<AANLkTiknZi97dDwm7sHqy0EL7tpNEP9sY5uPV6AN+q=u@mail.gmail.com >
<4D499E55.4020107@vmsinfo.com >
<4D49A6B9.4060608@2ndquadrant.com >
<4D49C482.4010707@vmsinfo.com >
<4D49F0BA.9000901@2ndquadrant.com >
<4D4A16BF.1020304@vmsinfo.com >
<4D4A4844.3020409@2ndquadrant.com >
<4D4AD9F6.6040903@vmsinfo.com >
<4D4AE16E.9040807@peak6.com >
<4D4B17B4.9030406@vmsinfo.com >
<4D4B1F5B.4060403@peak6.com >
<4D4B261B.6010303@vmsinfo.com >
<AANLkTi=6_7N4EuT-trfPbxb9UmanJsnL+ineO-iJUFtJ@mail.gmail.com >
<4D4B2E8A.7010402@vmsinfo.com >
<4D4B3395.6010007@agliodbs.com >
<4D4B394E.9080505@vmsinfo.com >
<4D4B5A73.3080302@agliodbs.com >
<AANLkTikCG8QUGpt7X=WEBnQCOio=R=zMLa_AoH4KCG2J@mail.gmail.com >
<AANLkTi=tUc33HgqKdZOYVsaLSp0zQ7eeMyb+HcTWdNfH@mail.gmail.com >
<AANLkTim+D5W3OyFWmXi0BA9xvP5yb5+Aja+Yfq0yOUFZ@mail.gmail.com >
<4D5504E5.3060901@gmail.com >
<AANLkTikwHQO2TVBYu81CLsBPjcyin3xrK+o7r=WrJ3g7@mail.gmail .com >
On 02/11/2011 12:26 PM, Tobias Brox wrote:
> 2011/2/11 Vitalii Tymchyshyn<tivv00@gmail.com>:
>>> My idea as well, though it looks ugly and it would be a maintenance
>>> head-ache (upgrading the index as new transaction types are added
>>> would mean "costly" write locks on the table,
>>
>> Create new one concurrently.
>
> Concurrently? Are there any ways to add large indexes without
> blocking inserts to the table for the time it takes to create the
> index?
yep, AFAIR since 8.2
see: http://www.postgresql.org/docs/8.2/static/sql-createindex.html#SQL-CREATEINDEX-CONCURRENTLY
[cut]
Andrea
view thread (26+ messages) latest in thread
Message-ID: <4D551E82.7030300@opinioni.net>
Permalink: ../4D551E82.7030300@opinioni.net/
Also on: postgresql.org/message-id/4D551E82.7030300@opinioni.net
copy link · copy postgr.es
reply 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-performance@postgresql.org
Cc: sickpig@opinioni.net, tobixen@gmail.com, tivv00@gmail.com, josh@agliodbs.com, mladen.gogala@vmsinfo.com
Subject: Re: Why we don't want hints Was: Slow count(*) again...
In-Reply-To: <4D551E82.7030300@opinioni.net>
* 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