Michael Guerin <[EMAIL PROTECTED]> writes:
> FATAL: block 26 of 1663/17228/3425958479 is still referenced (local 2)
> LOG: server process (PID 1887) exited with exit code 1
After some contemplation of the source code I was able to isolate a
possibly-related failure case:
regression=# create tem
Added to open items list:
* Tablespace
o add new GUC default_tablespace to control object creation when
no explicit TABLESPACE clause exists
Use it in pg_dump.
o Remove tablespace default for databases and schemas
Place objects as specified by the
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Magnus Hagander wrote:
>> Probably doable, but it requires API additions, I think.
> I thought about this. There are a lot of pointers in PGconn, and most
> we don't use so I don't like the idea of adding a new API to copy the
> complex PGconn structure
Magnus Hagander wrote:
> It won't work unless you make it a copy, I think. Because you'd have to
> lock the entire structure whenever you called PQexec() (since you don't
> know when PQexec does things), and that's just the time when you'd need
> to use it from the other thread...
>
> As for makin
Neil Conway <[EMAIL PROTECTED]> writes:
> So I'd like to add a GUC variable called something like
> "scratch_tablespace". If undefined (the default), temporary files for
> sorting/etc. will be created in the current database's tablespace.
(1) What are the protection requirements for this variable?
[EMAIL PROTECTED] wrote:
> On Thu, 28 Oct 2004, Bruce Momjian wrote:
>
> > Date: Thu, 28 Oct 2004 19:58:56 -0400 (EDT)
> > From: Bruce Momjian <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Cc: Tom Lane <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> > Subject: Re: [HACKERS] Unixware 714 pthreads
> >
On Thu, 28 Oct 2004, Bruce Momjian wrote:
> Date: Thu, 28 Oct 2004 19:58:56 -0400 (EDT)
> From: Bruce Momjian <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: Tom Lane <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Unixware 714 pthreads
>
> [EMAIL PROTECTED] wrote:
> > I agree wi
Hello:
I have the same problem as Welly, when try to connect PostgreSQL it cause
an error "unable to load libsqlpg.so".
I am using postgresql 7.4.1 and Debian Sarge with kernels 2.4.27 and 2.6.8-1.
A few weeks ago I get the connection work using Debian Woody with kernel 2.20,
but I had to make the
