Hi!
When postgres will use posix threads or support pool of backends (like apache)?
I guess it will increase speed very fast.
Using posix threads may increase data base engine using own internal locking
system againgst system locks.
Postgres is good database, but its too slow...
SKiller
--
On Mon, 29 Nov 1999 [EMAIL PROTECTED] wrote:
> When postgres will use posix threads or support pool of backends (like apache)?
> I guess it will increase speed very fast.
I am pretty sure it wouldn't. Postgres is slow (I think you compare it
to MySQL) because it has all moder features MySQL la
On Mon, 29 Nov 1999 [EMAIL PROTECTED] wrote:
> Its wrong solution to fork/exec backend each time. Especially for www-oriented
> software which need many short-time connection/work/desconnection. Using
> persistent connection is not always possible...
I wonder how Oracle handles this. I rememb
Hi!
On 29-Nov-99 Oleg Broytmann wrote:
> On Mon, 29 Nov 1999 [EMAIL PROTECTED] wrote:
>> Its wrong solution to fork/exec backend each time. Especially for
>> www-oriented
>> software which need many short-time connection/work/desconnection. Using
>> persistent connection is not always possible...
On Mon, 29 Nov 1999 [EMAIL PROTECTED] wrote:
> When postgres will use posix threads or support pool of backends (like apache)?
> I guess it will increase speed very fast.
Actually, the current model greatly benefits multiprocessor machines on
certain free operating systems (which are our best cu
Hi!
On 29-Nov-99 Peter Eisentraut wrote:
> On Mon, 29 Nov 1999 [EMAIL PROTECTED] wrote:
>
>> When postgres will use posix threads or support pool of backends (like
>> apache)?
>> I guess it will increase speed very fast.
>
> Actually, the current model greatly benefits multiprocessor machines o
On Mon, 29 Nov 1999 [EMAIL PROTECTED] wrote:
> Yes! But I recommend backend pool too. What is it? The postmaster task runs now
> backend for each query. Good. But After query backend finished. I recommend to
> stay backend running within a some timeout. If the next query occured
> the postmaster r
I'm not concern very much about speed of Postgres but mostly
about its connection schema. Every new connect to database postgres
forks another children. It's impossible to work with different
databases. On my production site I work with persistent connections
between http (mod_perl) <-> postgres a
On Mon, 29 Nov 1999, Oleg Bartunov wrote:
> I'm not concern very much about speed of Postgres but mostly
> about its connection schema. Every new connect to database postgres
> forks another children. It's impossible to work with different
> databases. On my production site I work with persistent
Hi!
OS: FreeBSD 3.3 stable
PG: 6.5.2 from ports collection
1. I create a database from my script and must GRANT all
tables, subsequences, indexes (amount 100) to some users I need.!
Yehh... GRANT does not allow me to grant all tables during one query.
If there any function(procedure) to do this
On Mon, 29 Nov 1999 [EMAIL PROTECTED] wrote:
> Using 6.3 I had troubles with php (as module) and persistent connection to
> postgresql. The backend fails after 2-3 requests after second pg_pconnect()
> call... Hmmm... May be it was php mistake...
If v6.3 is what you are using as a speed comparis
What version of PostgreSQL? Each version we've released has been faster
then the previous releases...
On Mon, 29 Nov 1999 [EMAIL PROTECTED] wrote:
> Hi!
>
> When postgres will use posix threads or support pool of backends (like apache)?
> I guess it will increase speed very fast.
>
> Using p
On Mon, 29 Nov 1999, Oleg Broytmann wrote:
> On Mon, 29 Nov 1999 [EMAIL PROTECTED] wrote:
> > When postgres will use posix threads or support pool of backends (like apache)?
> > I guess it will increase speed very fast.
>
>I am pretty sure it wouldn't. Postgres is slow (I think you compare i
On Mon, 29 Nov 1999 [EMAIL PROTECTED] wrote:
> Yes! But I recommend backend pool too. What is it? The postmaster task
> runs now backend for each query. Good. But After query backend
> finished. I recommend to stay backend running within a some timeout.
> If the next query occured the postmaster
> On Mon, 29 Nov 1999 [EMAIL PROTECTED] wrote:
>
> > Yes! But I recommend backend pool too. What is it? The postmaster task
> > runs now backend for each query. Good. But After query backend
> > finished. I recommend to stay backend running within a some timeout.
> > If the next query occured the
On 1999-11-29, Alexey V. Meledin mentioned:
> 1. I create a database from my script and must GRANT all
> tables, subsequences, indexes (amount 100) to some users I need.!
> Yehh... GRANT does not allow me to grant all tables during one query.
> If there any function(procedure) to do this for all
dear developers,
I've seen the replication skill on the todo-list. when will this be
released?
Or is it possibly with the actual build to synchronize two databases?
Thanks for your answers.
F. Röttger
Emsland Messe GmbH
BEGIN:VCARD
VERSION:2.1
N:Röttger;Florian
FN:Florian Röttger
ORG:Emsland
17 matches
Mail list logo
