c...@daemons.net writes:
> According to a Homebrew bug report
> (https://github.com/mxcl/homebrew/issues/11162):
> "You should submit a bug report to PostgreSQL as they can't assume Python is
> always built as a Framework on Darwin. They should be using python-config to
> get the gory details."
Hm
On Mon, May 07, 2012 at 05:31:40PM +0100, tom Tom wrote:
> Nope, this was just a benchmark script that caused this, any sane person
> would use an intbig index instead I guess. A better error message would be
> nice though, I was pretty confused when this happened.
>
> This can also bring down pos
On Thu, Apr 26, 2012 at 9:12 PM, Tom Lane wrote:
> I wrote:
>> Ryan Kelly writes:
>>> In my mind, all of these should have been rejected as erroneous input.
>>> To that end, I have attached a patch which causes all of these inputs
>>> to be rejected as invalid.
>
>> Hm, I would have expected all
On Wed, May 2, 2012 at 6:29 PM, Tom Lane wrote:
> The only way we could suppress such warnings would be if we made
> tab-complete.c use E'' strings for literals containing name prefixes;
> which is perhaps doable but it would mean having tab-complete.c roll
> its own string escaping rather than us
On Mon, May 7, 2012 at 6:06 PM, Tom Lane wrote:
> ig...@pow.lt writes:
>> [ you can sabotage foreign key constraints with triggers ]
>
> This is not a bug, it's a "don't do that" issue. The only way to
> prevent it would be to not fire triggers during FK operations, or
> to somehow restrict what
Nope, this was just a benchmark script that caused this, any sane person
would use an intbig index instead I guess. A better error message would be
nice though, I was pretty confused when this happened.
This can also bring down postgresql - it happens occasionally and causes
the server to terminat
The following bug has been logged on the website:
Bug reference: 6633
Logged by: Clay McClure
Email address: c...@daemons.net
PostgreSQL version: 9.1.3
Operating system: Darwin / Mac OS X 10.7.3 (Lion)
Description:
According to the installation documentation, one can
Pooja Khobragade wrote:
> I guess I get this error because there are two versions of
> postgreSQL installed on the same machine.
It sounds like that may be part of the problem, or an improper or
incomplete attempt at an update to a new major version.
On the other hand, there is definitely mo
Heikki Linnakangas writes:
> We could rearrange the page splitting algorithm to release locks
> earlier, before traversing to the next parent level.
That seems like a good idea just on concurrency grounds; I'm worried
about both the performance implications and the risk of deadlock.
> I wrote a
On 05.05.2012 22:49, t...@tomforb.es wrote:
The following bug has been logged on the website:
Bug reference: 6629
Logged by: Tom Forbes
Email address: t...@tomforb.es
PostgreSQL version: 9.1.3
Operating system: Windows 7 64bit
Description:
On a test database with 10,000 row
ig...@pow.lt writes:
> [ you can sabotage foreign key constraints with triggers ]
This is not a bug, it's a "don't do that" issue. The only way to
prevent it would be to not fire triggers during FK operations, or
to somehow restrict what triggers are allowed to do, and either of
those cures would
The following bug has been logged on the website:
Bug reference: 6631
Logged by: Jimmy Carrero
Email address: picard_alfa_...@hotmail.com
PostgreSQL version: 9.1.2
Operating system: Windows 7 Ultimate
Description:
When the instalation program are finished the files co
Tom & Kevin,
Thanks for your reply. I guess I get this error because there are two versions
of postgreSQL installed on the same machine.
Regards,
Pooja
-Original Message-
From: Kevin Grittner [mailto:kevin.gritt...@wicourts.gov]
Sent: Friday, May 04, 2012 7:54 PM
To: Pooja Khobragade;
The following bug has been logged on the website:
Bug reference: 6632
Logged by: Ignas Mikalajunas
Email address: ig...@pow.lt
PostgreSQL version: 9.1.3
Operating system: Ubuntu 11.11
Description:
The snippet that reproduces the bug:
drop schema public cascade;
create
14 matches
Mail list logo
