More update
If I run the concurrent re index locally (psql session) it works fine, but
when run via a connection through php I get the error
Can't be slon, since I can do this locally, but why would postgres have an
issue with a remote connection?
the basic script:
$connectString = "host=serve
On Thu, Oct 8, 2009 at 11:55 AM, Tom Lane wrote:
> I wouldn't be too surprised if the LOCK is coming from some Slony
> operation or other. You might want to ask the slony hackers about it.
I've had issues like this. Shutting down the slon daemons before
running such commands would usually allow
Tory M Blue writes:
> *2009-10-07 22:18:02 PDT admissionclsdb postgres 10.13.200.70(46706) ERROR:
> deadlock detected*
> *2009-10-07 22:18:02 PDT admissionclsdb postgres 10.13.200.70(46706)
> DETAIL: Process 20939 waits for ShareLock on virtual transaction
> 16/43817381; blocked by process 1874.
Hey all, it's been a bit however I'm running into some issues with my
concurrent index
Always get this error during a concurrent index.
*2009-10-07 22:18:02 PDT admissionclsdb postgres 10.13.200.70(46706) ERROR:
deadlock detected*
*2009-10-07 22:18:02 PDT admissionclsdb postgres 10.13.200.70(
