On Mon, Sep 13, 2010 at 4:48 AM, Kesavan wrote:
> Hi
>
> OS : Windows XP Professional SP3.
> Due to some of our product limitation, right now we can't migrate to
> 8.4.4. Hence we have to stick to 8.4.0-1.
>
> Kindly provide me the root causes of this issue so that I can avoid
> those pitfalls. Al
On 13/09/10 17:10, Dave Page wrote:
> On Mon, Sep 13, 2010 at 4:48 AM, Kesavan wrote:
>> Hi
>>
>> OS : Windows XP Professional SP3.
>> Due to some of our product limitation, right now we can't migrate to
>> 8.4.4. Hence we have to stick to 8.4.0-1.
>>
>> Kindly provide me the root causes of this i
On Mon, Sep 13, 2010 at 11:12 AM, Craig Ringer
wrote:
> On 13/09/10 17:10, Dave Page wrote:
>> On Mon, Sep 13, 2010 at 4:48 AM, Kesavan wrote:
>>> Hi
>>>
>>> OS : Windows XP Professional SP3.
>>> Due to some of our product limitation, right now we can't migrate to
>>> 8.4.4. Hence we have to stic
Craig:
> I've added a FAQ entry for this, as we've had more people with odd ideas
> about updates lately. It needs a shorter title ;-) but otherwise should
> cover things.
>
> As usual, check/editing appreciated.
http://wiki.postgresql.org/wiki/FAQ#A_bug_I.27m_encountering_is_fixed_in_a_newer_mi
Hi
OS : Windows XP Professional SP3.
Due to some of our product limitation, right now we can't migrate to
8.4.4. Hence we have to stick to 8.4.0-1.
Kindly provide me the root causes of this issue so that I can avoid
those pitfalls. Also if the issue comes, is there any script to complete
the inst
The following bug has been logged online:
Bug reference: 5654
Logged by: Daniel Howard
Email address: cheesero...@yahoo.com
PostgreSQL version: 8.4.4
Operating system: Linux (Ubuntu 10.04.1)
Description:Deferred Constraints don't work
Details:
The command
SET CONSTR
"Daniel Howard" writes:
> The command
> SET CONSTRAINTS ALL DEFERRED
> seems to have no effect.
Yes it does. For instance, in your example setting the mode to deferred
will allow you to insert an items row that doesn't match any users row:
regression=# insert into items(user_id) values(42);
ERR
The correct way to do what he wants to do is
configure PYTHON=/usr/local/bin/python3.1 ... other options ...
On lör, 2010-09-11 at 17:22 -0700, Josh Berkus wrote:
> I discussed this report with James Pye already, and he beleives it's a
> configure script bug which should be fixed before release
Peter Eisentraut writes:
> The correct way to do what he wants to do is
> configure PYTHON=/usr/local/bin/python3.1 ... other options ...
Hm, maybe this isn't adequately documented? Or at least should be
cross-referenced where we talk about python2 vs python3?
regards, t
The following bug has been logged online:
Bug reference: 5655
Logged by: Nate Carson
Email address: nate1...@gmail.com
PostgreSQL version: 8.4.4
Operating system: linux 2.6.33-sabayon (gentoo)
Description:Composite Type Handles Null Incorrectly
Details:
I have been
10 matches
Mail list logo
