> If I gave you access to an SGI running PostgreSQL 7.3.2, would you
> be willing to log in and explore the problem "live"?
You bet. Do you have gdb installed?
regards, tom lane
---(end of broadcast)---
TIP 5: Have you che
Dear Tom,
>
>
> "Robert E. Bruccoleri" <[EMAIL PROTECTED]> writes:
> > The PostgreSQL backend core dumps reproducibly with a set of LOCK commands that
> > would normally deadlock.
>
> Can't duplicate that here, using either 7.3 branch or CVS tip. You sure
> you have a clean build?
Oh yes, the
Dear Neil,
>
> On Thu, 2003-03-20 at 19:26, Robert E. Bruccoleri wrote:
> > MIPS Pro 7.4 and MIPS Pro 7.3.1.3, 64 bit compilation model.
>
> I've seen some other people having troubles with PostgreSQL compiled
> with Mips Pro on IRIX/MIPS -- does the problem persist if you recompile
> PostgreSQL
On Fri, Mar 21, 2003 at 16:44:07 +0530,
DEEPANSHU GARG <[EMAIL PROTECTED]> wrote:
> Hi,
> We have a problem when logging in postgresql.
> We are setting the user id and password using Create User command.
> Now when we login the postgresql using
> $psql -U username databasename
> it does'nt prom
Hello pgsql-bugs,
It seems that pgsql Makefiles lack the notion of pthreads or the
like libraries. I am using a threaded bind library, and when I
compile postgres it fails, since it can not find some routines.
Adding -lpthread to the LIBS= line in src/Makefile.global helps.
I am left won
Hi,
I manage several databases PostgreSQL 7.3.1 and I have noticed a problem.
When I delete many rows (with OID) the free space of disk doesn't changed !
I make a vacuumdb, but I doesn't notice an increase of the free space disk.
In a last step, I make a backup and a restoration but, it's the same
Hi,
We have a problem when logging in postgresql.
We are setting the user id and password using Create User command.
Now when we login the postgresql using
$psql -U username databasename
it does'nt prompt for the password but connects to the database.
The password is correctly set and we examined
Title: Possible bug with regards to multiple persistant connections
The operating environment in which this occurred is:
Apache 1.3.27
PHP 4.2.3
PostgreSQL 7.3.2
Redhat Linux 7.2
ADODB for PHP version 3.10
I have a database with an associated owner. I
[EMAIL PROTECTED] wrote:
Daniel Brozek ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description problem with returning setof with double precision
values
Long Description I have got the table and the function (look at
example code). Afte
[EMAIL PROTECTED] writes:
> SELECT INTO l_service service* FROM service
> WHERE service.service_id = l_service_id;
Shouldn't that just be
SELECT INTO l_service * FROM service
WHERE service.service_id = l_service_id;
Or possibly
SELECT INTO l_s
"Diego Cattelan" <[EMAIL PROTECTED]> writes:
> gesart=3D>alter table a add column c integer references xxx(id);
> =20
> NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
> ALTER TABLE
> =20
> The table xxx doesn't exist.
> =20
> Is that correct or postgreSQL shoul
Daniel Brozek ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
problem with returning setof with double precision values
Long Description
I have got the table and the function (look at example code). After executing this
functio
Title: Messaggio
template1=#create database
gesart;
template1=#create user
xuser;
template1=# \c gesart xuser
gesart=>create
table a(n integer);
CREATE
TABLE
gesart=>alter table a add column c integer
references xxx(id);
NOTICE: ALTER TABLE
will create implicit trigger(s) for FOR
13 matches
Mail list logo
