Woops, I forgot to say that of course I use a connection pooling.
Just 5 connections are pooled.
How many http connections per second are you getting?
200
Uh, so all of those http connections have to wait till one of the five
database connections is free? Maybe that's your bottleneck.
- Original Message -
From: "Rajit Singh" [EMAIL PROTECTED]
Hi,
I just have a small question. I discovered the psql -q option, which is
great... but I wanna get rid of *all* output that isn't something I need to
look at after the 1000th time I've run a particular echo 'blah' | psql.
Descriptions of the system tables can be found here:
http://www.postgresql.org/devel-corner/docs/postgres/catalogs.htm
Also, if you want to muddle through some PHP code, you can get phpPgAdmin
and checkout how the database and table structures are retrieved. It's all
done with standard
Hello,
I am using PostgreSQL v7.0.2. I compiled myself with gcc/g++ v2.7.2.2 on
Solaris 2.5.1. In libpq++, I get compiler warnings complaining that
namespaces are mostly broken in this version of g++. When I attempt to run a
piece of client code that was linked with libpq++.so, I get a symbol
Wade D. Oberpriller writes:
pgconnection.h:46: warning: namespaces are mostly broken in this version of g++
That's probably a good hint to upgrade your compiler.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
Steve Leibel writes:
I'm converting a mysql database to postgres. Is there an equivalent
for the enum data type?
No, but you can put the enum data in a separate table and join
them. This also makes the operation of adding entries to the enum list
better defined.
Dan
I have not tried prepareCall with postgreSQL but it makes sense
that it would not be implemented.
prepareCall is a JDBC method used to call stored procedures in a database.
postgreSQL implements stored procedures as function calls.
So up to now the prepareCall method has not been needed
Unless your application logic tries to use OIDs as row identifiers,
duplicate OIDs in user tables are not a problem.
Hmmm, that means that the following, which I use, is not strictly correct :
create table t1 (recordid SERIAL PRIMARY KEY, val INT4, name TEXT);
... much later ...
insert into
I just discoverred arrays, and I'm wondering if there's a way to do,
given table t1 (v int4, a int4[]), a query that does in effect :
"select v, i from t1 where EXISTS i SUCHTHAT a[i] = 45;"
I know I can do it with a separate table and a join, but this would
be much nicer.
Also, I wanted to
Best, depending on the scenario. In cases where you are using a fixed number
of characters, there's no need for the overhead of a varchar. For instance
if you are storing state abbreviations, they will ALWAYS be 2 characters.
The database can look up those fixed fields
Is there way to change default event error
messages thrown by the pgsql server
i.e. ERROR: unnamed referential integrity
violation - key in table_1_name still referenced from table_2_name
This for translation pourposes,avoiding
writing code on the client side...??, else ..does the server
I have a table where I need to select elements that are between
certain values. The typical query would be like:
select foo from bar where
element1 between ? and ? and -- using some val_1a and val_1b
element2 between ? and ? and -- using some val_2a and val_2b
...
On Fri, 19 Jan 2001, Florent Guillaume wrote:
I just discoverred arrays, and I'm wondering if there's a way to do,
given table t1 (v int4, a int4[]), a query that does in effect :
"select v, i from t1 where EXISTS i SUCHTHAT a[i] = 45;"
I know I can do it with a separate table and a join,
Sorry if I missed something.
El Vie 19 Ene 2001 11:08, Florent Guillaume escribi:
Unless your application logic tries to use OIDs as row identifiers,
duplicate OIDs in user tables are not a problem.
Hmmm, that means that the following, which I use, is not strictly correct :
create table
Harrelson, CulleyX writes:
Is there any difference between varchar and text other than varchar places a
cap on the number of characters?
Varchar is SQL compliant, Text is not. You can use Varchar without a
character limit, but that is not SQL compliant either.
--
Peter Eisentraut
select recordid from t1 where oid = $lastoid;
Because the last select could return several lines.
Shouldn't! oids are unique over the whole database server (I'm right on
this?) So you should have only one or non.
Well, no, that's the point of this whole discussion. If you give it
enough
I was just wondering if using views offered any sort of a performance
increase when designing my database.
Shawn
El Lun 22 Ene 2001 17:56, Florent Guillaume escribi:
select recordid from t1 where oid = $lastoid;
Because the last select could return several lines.
Shouldn't! oids are unique over the whole database server (I'm right on
this?) So you should have only one or non.
Well, no, that's
message resent to [EMAIL PROTECTED]
On Fri, 19 Jan 2001, Joel Bernstein wrote:
I have not tried prepareCall with postgreSQL but it makes sense
that it would not be implemented.
prepareCall is a JDBC method used to call stored procedures in a database.
postgreSQL implements stored
Does postgresql have a time type that supports miliseconds?
Nelio
--
Nelio Alves Pereira Filho
IFX Networks - www.ifx.com.br
+55 11 3365-5863
[EMAIL PROTECTED]
Well, no, that's the point of this whole discussion. If you give it
enough time, oids can wrap around, which apparently doesn't affect the
functionning of the database but application that depend on unique oids
could get hosed.
Yes, the documentation is wrong.
Wow. I guess we need
Kyle [EMAIL PROTECTED] writes:
I have a table where I need to select elements that are between
certain values. The typical query would be like:
select foo from bar where
element1 between ? and ? and -- using some val_1a and val_1b
element2 between ? and ? and -- using
Florent Guillaume [EMAIL PROTECTED] writes:
If, however, like someone else on this list, you have an application
that does 200 requests per second, and that each request generates two
updates, that's 144 oids consumed per hour, 3456 per day,
1261440 per year, oops that's more than
Florent Guillaume [EMAIL PROTECTED] writes:
If, however, like someone else on this list, you have an application
that does 200 requests per second, and that each request generates two
updates, that's 144 oids consumed per hour, 3456 per day,
1261440 per year, oops that's more
Bruce Momjian [EMAIL PROTECTED] writes:
What about pre-fetching of OID's. Does that still happen for every
backend?
Only ones that actually allocate some OIDs, I think.
What about XID's?
XIDs are wasted on a postmaster restart, but not per-backend, because
they are cached in shared memory
Rather than writing PostgreSQL data entry screens
from scratch using ncurses and cdk, is anyone aware of any data entry screen
building utilities useful for character-based screens, as opposed to GUI
utilities?
Tim
I haven't used PL/pgSQL very much but it looks like a good language in which
to make some simple functions for this application I'm writing..
Is it possible (with PL/pgSQL) to access other records in other tables than
the tuple that pulled the trigger (and called the function)?
Say this (pseudo
Bruce Momjian [EMAIL PROTECTED] writes:
What about pre-fetching of OID's. Does that still happen for every
backend?
Only ones that actually allocate some OIDs, I think.
What about XID's?
XIDs are wasted on a postmaster restart, but not per-backend, because
they are cached in
Er, I'm pretty sure I found what I was looking for, sorry to waste
everyone's time.. I looked right past half the documentation!
-Mitch
- Original Message -
From: "Mitch Vincent" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, January 22, 2001 6:56 PM
Subject: PL/pgSQL Question
Bruce Momjian [EMAIL PROTECTED] writes:
What about pre-fetching of OID's. Does that still happen for every
backend?
Only ones that actually allocate some OIDs, I think.
What about XID's?
XIDs are wasted on a postmaster restart, but not per-backend, because
they are cached in
On Mon, Jan 22, 2001 at 03:14:36PM -0800, Tim Barnard wrote:
Rather than writing PostgreSQL data entry screens from scratch using
ncurses and cdk, is anyone aware of any data entry screen building
utilities useful for character-based screens, as opposed to GUI
utilities?
I had never heard
Added to TODO:
* Move OID retrieval into shared memory to prevent lose of
unused oids
Already implemented. But - up to 8192 oids may be lost in the event
of crash (ie without normal database shutdown when last fetched oid
is logged to WAL).
Also, currently the oid can _not_ be used to
32 matches
Mail list logo