Alvaro,
Is there a PostgreSQL bug number that I could refer to for this problem?
Thank you.
On Tue, Jul 9, 2013 at 4:53 PM, Alvaro Herrera wrote:
> Jamey Poirier escribió:
> >
> > Thank you Alvaro. Yes, this explains it.
> > It doesn't help to fix it but at least I know now that it's a known
Doing that just moves the problem from the time of the UPDATE to the time
of the COMMIT.
It is still possible to get a deadlock and I'm not sure how making it
deferrable helps in this case.
You can still end up with a deadlock like this:
CON1: BEGIN;
CON1: SELECT * FROM A WHERE id = 1 FOR UPDATE;
The following bug has been logged on the website:
Bug reference: 8105
Logged by: András Kolesár
Email address: p...@kolesar.hu
PostgreSQL version: 9.1.5
Operating system: Windows
Description:
If I specify an unicode field name without quotes, field name gets lowecase
The following bug has been logged on the website:
Bug reference: 7754
Logged by: Gavan Schneider
Email address: pg-...@snkmail.com
PostgreSQL version: 9.2.2
Operating system: OSX
Description:
FILE:
postgresql-9.2.2/contrib/start-scripts/osx/PostgreSQL ; and
many
The following bug has been logged on the website:
Bug reference: 7651
Logged by: Morten Minde Neergaard
Email address: m...@8d.no
PostgreSQL version: 9.1.6
Operating system: Debian Wheezy
Description:
Bug: When making an index over a function, then selecting a result
Ok. I've reproduced this but I now think that it isn't a bug.
My schemas initially weren't the symetric when I was using select *. Alas,
when I did align my schemas later, I had already switched to specifying a
column list which then did not match the column list in the table. An
improvement
