On Wed, Sep 03, 2003 at 12:03:59AM -0400, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > I don't entirely understand all of what that code is doing, but I think
> > there's something in there that needs to get fixed.
>
> Oh-ho, this is interesting:
>
> Build CVS tip on RHL 8.0 wi
sad wrote:
> On Monday 01 September 2003 20:57, you wrote:
> > sad wrote:
> > > Good day
> > >
> > > is it possible to define user variables in session ?
> > > If not then is it planned to implement ?
> > > or it is principially impossible in PosqtgreSQL
> >
> > psql has variables, but in general w
The problem:
1) I create a stupid function like:
CREATE FUNCTION p4() RETURNS integer AS '
BEGIN
FOR i IN 1..100 LOOP
insert into info values (random(),random());
END LOOP;
RETURN 1;
END;
' LANGUAGE plpgsql;
2) I create a new db and run "select p4();"
3) I open three connection to the same db
We just fixed this so our next beta will be correct. CVS already has
the fix.
---
Janko Richter wrote:
> On FreeBSD 5.1 using PgSQL 7.4b2 initdb failed with:
>
> su-2.05b$ ./initdb -D /data/pgsql
> The files belonging to t
Janko Richter <[EMAIL PROTECTED]> writes:
> On FreeBSD 5.1 using PgSQL 7.4b2 initdb failed with:
Yeah, it's broken on any system with shmmax too small for the
defaults :-(. My fault.
> This patch solves the problem:
It's fixed in a different way in CVS tip.
regards, tom
andrea gelmini <[EMAIL PROTECTED]> writes:
> 3) I open three connection to the same db and start operation as
>"begin work; select p4(); update info set data=RANDOM();commit;"
>"create index gino on info(x);"
>"begin work; update info set data=RANDOM();"
>Well, db schema is nothink
On FreeBSD 5.1 using PgSQL 7.4b2 initdb failed with:
su-2.05b$ ./initdb -D /data/pgsql
The files belonging to this database system will be owned by user
"postgres".
This user must also own the server process.
The database cluster will be initialized with locale C.
fixing permissions on existing
