FYI: I've been working off-list with Mehul to solve this, and we've
pinpointed the reason. The affected machine had the "INTERACTIVE USERS"
pseudo-group in "Power Users". Another group we have to check for in the
next version of the installer, and I'll update the FAQ with this.
(Previously we check
Frank van Vugt <[EMAIL PROTECTED]> writes:
> Meanwhile, one of the application developers here bumped into a way to
> reproduce what looks like the same memory alloc problem (exactly the same
> point in exactly the same trigger) using our application software
> only,
Oh good. Can you construct
> > Meanwhile, one of the application developers here bumped into a way to
> > reproduce what looks like the same memory alloc problem (exactly the same
> > point in exactly the same trigger) using our application software
> > only,
>
> Oh good. Can you construct a self-contained test case then?
Frank van Vugt <[EMAIL PROTECTED]> writes:
>> This is the expected case. The failure in CopySnapshot has got to
>> indicate that somebody set one or the other field to some bizarrely
>> large value, though. I take it you didn't run the watchpointed backend
>> far enough to get the memory-alloc er
Stephan Szabo wrote:
On Thu, 2 Dec 2004, postgresbugs wrote:
On Wed, 1 Dec 2004, Stephan Szabo wrote:
On Wed, 1 Dec 2004, postgresbugs wrote:
> Foreign keys referencing parent table fails on insert if the key is in
the table that inherits the parent table.
Oliver Elphick wrote:
> I think this has been fixed in 8.0beta5, but you may want to apply
> the patch to the 7.4 tree. I can't access developer.postgresql.org
> to check the cvs; that server seems to be down at the moment.
I've checked in the fix for 7.4. 8.0 had already been corrected.
--
Pe
Hello:
Since 5.6 or so, perl has stored an internal flag on every string to
mark whether it's UTF-8 or not. For data of unknown encoding, such as
data read from files, the default is latin1, but it can be changed with
use encoding 'utf8'. Now, I have a postgresql database in charset
UNICODE. So
David Kamholz <[EMAIL PROTECTED]> writes:
> This is rather kludgy, considering there already
> exists a way to fix it by calling the libperl API properly.
If you know how to do it, how about offering a patch?
regards, tom lane
---(end of broadcast
> [ scratches head ... ] AFAICS, the CopySnapshot that gets the error
> must be trying to copy one or the other of those snapshots. Maybe you
> should look at the address passed to CopySnapshot and see what it's
> really pointing at, and where it came from.
Ok, stepping through the transaction d
Frank van Vugt <[EMAIL PROTECTED]> writes:
> The only thing I can think of is that the handling of pol X and creation of
> pol Y from within spawn_pol() is somehow messing things up, but..
Certainly the mere firing of a deferred trigger isn't the problem; we do
that all the time. What struck
> > The only thing I can think of is that the handling of pol X and creation
> > of pol Y from within spawn_pol() is somehow messing things up, but..
> Certainly the mere firing of a deferred trigger isn't the problem; we do
> that all the time.
Me too ;)
I was more trying to emphase the mul
11 matches
Mail list logo
