have /usr/ucb before /bin in path to
get the 'correct' behaviour from commands like df and ps...)
_
Mats Lofkvist
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
el by multiple threads.
(Quick and dirty patch below.)
(The method also isn't using the 'length' parameter correctly,
but since offset always seems to be zero, this bug doesn't show up.)
_
Mats Lofkvist
[EMAIL PROTECTED]
*** org/postgresql/core/Encoding.java~ Sun Oct
Pages 1; Tuples 0.
CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO: Analyzing public.attribute
VACUUM
mats=#
_
Mats Lofkvist
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
now enough of the
postgres internals to suggest a usable solution for this
problem. Thanks for your quick answers.
_
Mats Lofkvist
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[EMAIL PROTECTED] (Tom Lane) writes:
> Mats Lofkvist <[EMAIL PROTECTED]> writes:
> > [EMAIL PROTECTED] (Tom Lane) writes:
> >> 7.3 will be smarter about this.
>
> > Seems like I get the same behaviour with 7.3 beta1, updating
> > the same row ~20k time
[EMAIL PROTECTED] (Tom Lane) writes:
> Mats Lofkvist <[EMAIL PROTECTED]> writes:
> > But when doing ~1000 updates (i.e. setting val0 and val1 with
> > a where on an existing key0/key1/key2 triplet), I get this which
> > seems very strange to me:
>
> I suppose yo
[EMAIL PROTECTED] (Tom Lane) writes:
> Mats Lofkvist <[EMAIL PROTECTED]> writes:
> > But when doing ~1000 updates (i.e. setting val0 and val1 with
> > a where on an existing key0/key1/key2 triplet), I get this which
> > seems very strange to me:
>
> I suppose yo
en
doing an update seems strange by itself, but shouldn't be
a problem if it was just done as efficiently as when doing
an insert.)
_
Mats Lofkvist
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
[EMAIL PROTECTED] (Andrew Sullivan) writes:
> On Thu, Jul 11, 2002 at 11:15:42PM -0400, Tom Lane wrote:
> > Mats Lofkvist <[EMAIL PROTECTED]> writes:
> > > When testing postgres 7.2.1 on a sparc/solaris8 box with
> > > --enable-locale --enable-multibyte I get a cr
val = xfrmstr;
2061#endif
2062
2063return (unsigned char *) val;
(gdb) down
#0 0x269bd0 in pfree (pointer=0x4b7878) at mcxt.c:446
446 AssertArg(MemoryContextIsValid(header->context));
(gdb) print header
$7 = (StandardChunkHeader *) 0x4b7868
(gdb) print *header
$8 = {cont
10 matches
Mail list logo
