Re: [ADMIN] performance issue using DBI

2002-06-06 Thread nikolaus
Nicolas, The more data your tables contain the more work PostgreSQL needs to do. Adding indexes on your tables makes the INSERTS slower due to additional overhead. Indexes speed up SELECT but slow down INSERT. Therefore OLTP systems tend to have few indexes and data warehouses many. Instead o

Re: [ADMIN] pg_shadow

2002-06-06 Thread Mark McEahern
[Kasper] > Do i have to create the pg_shadow table myself or how do i do, > the password auth is not worjing. > > and i think i need HELP... It would help if you were a little more specific: 1. What exactly are you doing? 2. What exactly do you mean by "is not working"? Have you modified pg_h

Re: [ADMIN] [pgadmin-support] Cache lookup error

2002-06-06 Thread Dave Page
> -Original Message- > From: Marc Mitchell [mailto:[EMAIL PROTECTED]] > Sent: 05 June 2002 23:44 > To: Dave Page; Ramya Asokan; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: Re: [ADMIN] [pgadmin-support] Cache lookup error > > > I've been experiencing this same problem and think

[ADMIN] pg_shadow

2002-06-06 Thread Kasper
Do i have to create the pg_shadow table myself or how do i do, the password auth is not worjing. and i think i need HELP... /K ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

Re: [ADMIN] [GENERAL] performance issue using DBI

2002-06-06 Thread Lee Green
If you need to get the actual "current value" without incrementing, try: SELECT last_value FROM ; This will return the last value returned from a nextval command directly from the sequence properties in the system tables. -Original Message- From: Dan Langille [mailto:[EMAIL PROTECTED]

Re: [ADMIN] [GENERAL] performance issue using DBI

2002-06-06 Thread Dan Langille
On 6 Jun 2002 at 17:14, Oliver Elphick wrote: > On Thu, 2002-06-06 at 14:55, Joshua b. Jore wrote:u > > Don't use currval since some other process might alter the > > sequence between the time you call nextval and currval. > > This is wrong. currval() will always return the last serial a

Re: [ADMIN] [GENERAL] performance issue using DBI

2002-06-06 Thread Oliver Elphick
On Thu, 2002-06-06 at 14:55, Joshua b. Jore wrote:u > Don't use currval since some other process might alter the > sequence between the time you call nextval and currval. This is wrong. currval() will always return the last serial assigned in *the*same*session*. It is not affected by oth

Re: [ADMIN] About a PL/pgSQL function

2002-06-06 Thread Joel Burton
On Thu, 6 Jun 2002, Ferdinand Smit wrote: > When i create a function with a "static" table name, it works fine. > EXECUTE does not allow SELECT INTO, so does anyone have an other solution? Use: DECLARE cursorname refcursor; varname int; BEGIN OPEN cursorname FOR EXECUTE ''SELECT ... FROM

[ADMIN] performance issue using DBI

2002-06-06 Thread Nicolas Nolst
Hi all,I have developped a perl script to populate a database with two tables: sessionsand actions.the table actions contains the following columns: session_id, url, timestamp.The column session_id references to the table sessions.the table sessions contains the following columns: session_id, remo