This just hit us today... Admittedly on an old cluster still running 9.2,
though I can't see any mention of it being addressed since.
Any chance of getting this on to to-do list?
On Sat, 1 Nov 2014 at 07:45, Simon Riggs wrote:
> On 31 October 2014 17:46, Michael Banck
On 31 October 2014 17:46, Michael Banck michael.ba...@credativ.de wrote:
I wonder whether that is pilot error (fair enough), or whether something
could be done about this?
When originally written the constraints were tighter, but have since
been relaxed.
Even so a CIC waits until all
I have not kept up with PostgreSQL changes and have just been using it. A
co-worker recently told me that you need to word CONCURRENTLY in CREATE
INDEX to avoid table locking. I called BS on this because to my knowledge
PostgreSQL does not lock tables. I referenced this page in the
documentation:
On 10/31/2014 10:28 AM, Mark Woodward wrote:
I have not kept up with PostgreSQL changes and have just been using
it. A co-worker recently told me that you need to word CONCURRENTLY
in CREATE INDEX to avoid table locking. I called BS on this because
to my knowledge PostgreSQL does not lock
On Fri, Oct 31, 2014 at 2:28 PM, Mark Woodward
mark.woodw...@actifio.com wrote:
I have not kept up with PostgreSQL changes and have just been using it. A
co-worker recently told me that you need to word CONCURRENTLY in CREATE
INDEX to avoid table locking. I called BS on this because to my
Am Freitag, den 31.10.2014, 14:43 + schrieb Greg Stark:
On Fri, Oct 31, 2014 at 2:28 PM, Mark Woodward
mark.woodw...@actifio.com wrote:
I have not kept up with PostgreSQL changes and have just been using it. A
co-worker recently told me that you need to word CONCURRENTLY in CREATE
Sorry to start another thread while we are still discussing CREATE
INDEX design, but I need help/suggestions to finish the patch on
time for 8.3
We earlier thought that CREATE INDEX CONCURRENTLY (CIC)
would be simpler to do because of the existing waits in CIC.
But one major problem with CIC is