Hi all
As I understand every time there is a request to
postgres a new backend is made, and when the request is finished, even if the
connection is already active the backend dies. I wonder if is there any
parameter that allow backends to remain beyond a transaction. Creating a new
backend
Make sure you have a clean copy of the source, Barry has done an
extensive re-organization to remove the duplicate code between jdbc1,
and jdbc2, to prepare for jdbc3.
It compiles clean on my machine using jdk1.3.1
Dave
On Sun, 2002-07-28 at 22:12, Tatsuo Ishii wrote:
It seems JDBC in current
- Original Message -
From: Robert E. Bruccoleri [EMAIL PROTECTED]
To: Luis Alberto Amigo Navarro [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, July 29, 2002 2:48 AM
Subject: Re: [HACKERS] Question about LWLockAcquire's use of semaphores
Just a long standing curiosity?
For most web sites MySQL seems to work fine, but overall PostgreSQL offers
more capabilites so why build upon a limited base such as MySQL?
Does anyone here have any idea as to why so many people select MySQL when
both systems are open sourced?
Matthew
1234567890
Hi!
I write function on plpgsql and have some troubles:
I have table owe : uid int4, date int4, cost float4;
I want to select into owe_old : DECLARE owe_old float4;
cur_date := date_part(''year'', now()) || ''-'' || date_part(''month'', now()) ||
''-01'';
we have cur_date =
Just a long standing curiosity?
For most web sites MySQL seems to work fine, but overall PostgreSQL offers
more capabilites so why build upon a limited base such as MySQL?
Does anyone here have any idea as to why so many people select MySQL when
both systems are open sourced?
Three
Given the GPL isn't wanted in the contrib directory, it may be wise to
take care of src/interfaces/odbc/license.txt
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Mon, 29 Jul 2002 [EMAIL PROTECTED] wrote:
[snip]
e) Inertia. MySQL got more popular way back when; the reasons may no longer
apply, but nobody is going to move to PostgreSQL without _compelling_ reason,
and you'll have to show something _really compelling_.
I would like to add one
well that and people tend to drift towards an easy answer,
like php... amazing how that combo is so popular... hrrmm...
Roderick A. Anderson writes:
On Mon, 29 Jul 2002 [EMAIL PROTECTED] wrote:
[snip]
e) Inertia. MySQL got more popular way back when; the reasons may no longer
On Mon, 29 Jul 2002, Chris Humphries wrote:
well that and people tend to drift towards an easy answer,
like php... amazing how that combo is so popular... hrrmm...
Well people seem to get so ... about php that I didn't want to touch that
topic.
Rod
--
Open Source Software - Sometimes
On Mon, 29 Jul 2002, Roderick A. Anderson wrote:
I would like to add one other thought. There are many web site
designers that get thrust into being a web site programmer. Without
an understanding of database design and a novice programmers (?) view
of the process the benefits of letting the
Have any organizations run TPC benchmarks against PostgreSQL other than
the old and much maligned GreatBridge benchmark? It is unfortunate that
there are not any moderately standard benchmarks available regarding
PostgreSQL. I do not need to say PgSQL is better than X, but it would
be nice to at
Hi,
I tried yuva_test1 left outer join yuva_test2 and yuva_test1 left outer join
yuva_test3 in the same query in Oracle. I tried the following query in
postgres and it worked...
select yt1_name, yt1_descr, yt2_name, yt2_descr, yt3_name, yt3_descr from
(yuva_test1 left outer join yuva_test2 on
Hi Paul,
You might want to take at look at the Open Source Database Benchmark
project:
http://www.sf.net/projects/osdb
This is an implementation (by Andy Riebs from Compaq) of the AS3AP
database benchmark, and works with PostgreSQL, MySQL, and one other
database too from memory. You're
Looks fine, you may want to rephrase it as:
select yt1_name, yt1_descr, yt2_name, yt2_descr, yt3_name, yt3_descr
from yuva_test1 left outer join yuva_test2 on yt1_id = yt2_id
left outer join yuva_test3 on yt1_id = yt3_id
to make it more legible. The alias is overkill in this
I had occasion (and a perfectly good reason) to install 7.1.3 on
a fresh server [1]. Installation succeeded as normal, data failed
to load because some relation names go beyond
31 characters. smack forehead, alter NAMEDATALEN,
recompile. initdb fails immediately after the message
creating
Ian Barwick [EMAIL PROTECTED] writes:
- Does src/include/postgres_ext.h count as a parser definition file?
No, it doesn't. Your experience sounds like you may have neglected to
do a full rebuild after altering NAMEDATALEN. (By default, we don't
compute object-file dependencies, so it's up to
The current ODBC drivers on the website don't appear to work with recent
development.
I'm able to login, but immediately after it throws the error 'Blank'
with a large negative number above (-2^16 or so).
I don't have Visual C, so would it be possible for someone to build a
new (working)
Can anyone fix this?
$ cvs up
can't create temporary directory /tmp/cvs-serv40296
No space left on device
--
Tatsuo Ishii
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
We've discussed at least a couple of times before that it would be nice
to be able to create stand-alone composite types. Tom mentioned that
ideally this would be done as part of a refactoring of system tables so
that attributes belonged to pg_type, instead of belonging to pg_class.
But it wasn't
What's with this manual page?
http://candle.pha.pa.us/main/writings/pgsql/sgml/gist.html
Seems like it's almost accidental - like a copied and pasted email. It
doesn't look like it should be there?
Chris
---(end of broadcast)---
TIP 5: Have
I've developed patches to be able to specify the location of the WAL
directory, with the default location being where it is now. The patches
define a new environment variable PGXLOG (a la PGDATA) and postmaster,
postgres, initdb and pg_ctl have been taught to recognize a new command
On Mon, Jul 29, 2002 at 11:28:54PM +0800, Christopher Kings-Lynne wrote:
libpq has a function pconnect as opposed to connect that will do it.
libpq has neither function, AFAIK.
As for persistent backends, it's on the TODO list, but I'm not aware
that anyone has put any work into implementing
Curt Sampson wrote:
I'm still waiting to find out just what advantage table inheritance
offers. I've asked a couple of times here, and nobody has even started
to come up with anything.
We inherited inheritance from Berkeley. I doubt we would have added it
ourselves. It causes too much
Bruce Momjian wrote:
Curt Sampson wrote:
I'm still waiting to find out just what advantage table inheritance
offers. I've asked a couple of times here, and nobody has even started
to come up with anything.
We inherited inheritance from Berkeley. I doubt we would have added it
On Mon, 29 Jul 2002, Bruce Momjian wrote:
Curt Sampson wrote:
I'm still waiting to find out just what advantage table inheritance
offers. I've asked a couple of times here, and nobody has even started
to come up with anything.
We inherited inheritance from Berkeley. I doubt we would
On Mon, 2002-07-29 at 11:32, Luis Alberto Amigo Navarro wrote:
Hi all
As I understand every time there is a request to postgres a new backend
is made, and when the request is finished, even if the connection is
already active the backend dies.
I think you have misunderstood it. A new backend
On Mon, 2002-07-29 at 19:01, Curt Sampson wrote:
On Mon, 29 Jul 2002, Bruce Momjian wrote:
Curt Sampson wrote:
I'm still waiting to find out just what advantage table inheritance
offers. I've asked a couple of times here, and nobody has even started
to come up with anything.
It is
On Mon, 2002-07-29 at 20:21, Luis Alberto Amigo Navarro wrote:
if i put debug_level=1 i get for one connect and several inserts on backend
die after each insert
What client do you use ?
--
Hannu
---(end of broadcast)---
TIP 4: Don't
libpq
PQsetdb(
- Original Message -
From: Hannu Krosing [EMAIL PROTECTED]
To: Luis Alberto Amigo Navarro [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, July 29, 2002 9:40 PM
Subject: Re: [HACKERS] question on backends
On Mon, 2002-07-29 at 20:21, Luis Alberto Amigo
On Mon, 2002-07-29 at 20:50, Luis Alberto Amigo Navarro wrote:
libpq
PQsetdb(
- Original Message -
From: Hannu Krosing [EMAIL PROTECTED]
To: Luis Alberto Amigo Navarro [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, July 29, 2002 9:40 PM
Subject: Re: [HACKERS]
Hi,
I've just managed to recover from a fun Postgres lock up experience!
Basically Postgres seemed to have hung, with a stack of idle postmaster
processes. There was an idle VACUUM process and an idle CHECKPOINT process
running as well.
I finally managed to get it restarted (after a reboot),
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
What's with this manual page?
http://candle.pha.pa.us/main/writings/pgsql/sgml/gist.html
GiST is, um, *very* poorly documented. Feel free to submit doc patches.
(I've just committed a few tidbits in xindex.sgml, but much more work
is needed.)
Looks like Tom got this in. Thanks.
---
Christopher Kings-Lynne wrote:
If Bruce is thinking of applying outstanding patches - whatever happened
with Bill Studenmund's CREATE OPERATOR CLASS patch?
Chris
Looks like Tom got this patch in. Thanks.
---
Bill Studenmund wrote:
On Sun, 14 Apr 2002, Bruce Momjian wrote:
Good question. I see the thread at:
OK, now I run it and it does absolutely nothing to the pg_stat_all_tables
relation for instance. In fact, it seems to do nothing at all - does the
reset function even work?
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tom Lane
Sent:
OK, now I run it and it does absolutely nothing to the pg_stat_all_tables
relation for instance. In fact, it seems to do nothing at all - does the
reset function even work?
OK, I'm an idiot, I was calling the funciton like this: void blah(void)
which actually does nothing.
It all works now
I've developed patches to be able to specify the location of the WAL
directory, with the default location being where it is now. The patches
define a new environment variable PGXLOG (a la PGDATA) and postmaster,
postgres, initdb and pg_ctl have been taught to recognize a new command
line switch
Hi guys,
When I try to do a cvs up I get this:
can't create temporary directory /var/tmp/cvs-serv39998
No space left on device
And on the 15min SGML docs site there's this:
Changes in this build:
can't create temporary directory /var/tmp/cvs-serv39998
No space left on device
Chris
Because of a runaway process on postgresql.org, CVS is working
intermittently, if at all. I have contacted Marc.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
We are in the process of refactoring how the port-specific files are
used in PostgreSQL. Please grab a newer CVS and give it a try. Thanks.
---
[EMAIL PROTECTED] wrote:
With pg 7.2 I had no problems, but getting the
Bruno Wolff III wrote:
On Fri, Jul 26, 2002 at 13:55:58 -0300,
Marc G. Fournier [EMAIL PROTECTED] wrote:
As an example ... at the University I work at, we've started to use PgSQL
for more and more of our internal stuff, and/or let the students start to
use it for their projects ...
Marc G. Fournier wrote:
Something to maybe add to the TODO list, if someone has the
time/inclination to work on it ...
The problem with the current auth system, as I see it, is that you can't
easily have seperate user lists and passwords per database ... its shared
across the system ...
On Mon, 29 Jul 2002, Bruce Momjian wrote:
Marc G. Fournier wrote:
Something to maybe add to the TODO list, if someone has the
time/inclination to work on it ...
The problem with the current auth system, as I see it, is that you can't
easily have seperate user lists and passwords per
Marc G. Fournier wrote:
On Mon, 29 Jul 2002, Bruce Momjian wrote:
Marc G. Fournier wrote:
Something to maybe add to the TODO list, if someone has the
time/inclination to work on it ...
The problem with the current auth system, as I see it, is that you can't
easily have
am looking at it now ... trying to figure out where we're using 30gig of
space righ tnow :(
On Tue, 30 Jul 2002, Christopher Kings-Lynne wrote:
Hi guys,
When I try to do a cvs up I get this:
can't create temporary directory /var/tmp/cvs-serv39998
No space left on device
And on the 15min
Robert E. Bruccoleri wrote:
Dear Tom,
Thank you for the explanation. I did not understand what was
going on in lwlock.c.
Yes, as Tom said, using the pre-7.2 code on SMP machines, if one backend
had a spinlock, the other backend would TAS loop trying to get the lock
until its timeslice
On Mon, 29 Jul 2002, Bruce Momjian wrote:
Actually, it is replaced by encrypted pg_shadow by default in 7.3, and
the new USER (users or groups) column in pg_hba.conf that will be in 7.3
that can restrict based on user/group. This replaces the use of the
secondary file for just usernames.
Marc G. Fournier wrote:
On Mon, 29 Jul 2002, Bruce Momjian wrote:
Actually, it is replaced by encrypted pg_shadow by default in 7.3, and
the new USER (users or groups) column in pg_hba.conf that will be in 7.3
that can restrict based on user/group. This replaces the use of the
Thomas Lockhart [EMAIL PROTECTED] writes:
I've developed patches to be able to specify the location of the WAL
directory, with the default location being where it is now. The patches
define a new environment variable PGXLOG (a la PGDATA) and postmaster,
postgres, initdb and pg_ctl have been
On Sun, 28 Jul 2002, Bruce Momjian wrote:
Marc G. Fournier wrote:
God, I go through 200+ of those almost daily as moderator ... imagine if
we had the lists open? :)
How do you prevent virus emails from coming in that look like they are
from the intended person? Does the filter check
On Sun, 28 Jul 2002, Marc G. Fournier wrote:
On 28 Jul 2002, Larry Rosenman wrote:
On Sun, 2002-07-28 at 20:10, Marc G. Fournier wrote:
God, I go through 200+ of those almost daily as moderator ... imagine if
we had the lists open? :)
I picked up a copy of McAfee's vscan for
Justuse persistent connections.
Chris
- Original Message -
From:
Luis Alberto
Amigo Navarro
To: [EMAIL PROTECTED]
Sent: Monday, July 29, 2002 5:32 PM
Subject: [HACKERS] question on
backends
Hi all
As I understand every time there is a request to
How?
- Original Message -
From:
Christopher Kings-Lynne
To: Luis Alberto Amigo Navarro ; [EMAIL PROTECTED]
Sent: Monday, July 29, 2002 12:36
PM
Subject: Re: [HACKERS] question on
backends
Justuse persistent
connections.
Chris
- Original
-Original Message-
From: Rod Taylor [mailto:[EMAIL PROTECTED]]
Sent: 29 July 2002 14:39
To: PostgreSQL-development
Subject: [HACKERS] GPL License
Given the GPL isn't wanted in the contrib directory, it may
be wise to take care of src/interfaces/odbc/license.txt
Take care
-Original Message-
From: Rod Taylor [mailto:[EMAIL PROTECTED]]
Sent: 29 July 2002 14:39
To: PostgreSQL-development
Subject: [HACKERS] GPL License
Given the GPL isn't wanted in the contrib directory, it may
be wise to take care of src/interfaces/odbc/license.txt
-Original Message-
From: Rod Taylor [mailto:[EMAIL PROTECTED]]
Sent: 29 July 2002 14:44
To: Dave Page
Cc: PostgreSQL-development
Subject: RE: [HACKERS] GPL License
-Original Message-
From: Rod Taylor [mailto:[EMAIL PROTECTED]]
Sent: 29 July 2002 14:39
To:
Dave Page [EMAIL PROTECTED] writes:
From: Rod Taylor [mailto:[EMAIL PROTECTED]]
Given the GPL isn't wanted in the contrib directory, it may
be wise to take care of src/interfaces/odbc/license.txt
Take care of it how? It can't be just removed as everything under
src/interfaces/odbc *is*
libpq has a function pconnect as opposed to connect
that will do it. PHP and most other interfaces will let you use persistent
connections.
Chris
- Original Message -
From:
Luis Alberto
Amigo Navarro
To: Christopher Kings-Lynne ; [EMAIL PROTECTED]
Sent: Monday,
On Mon, 29 Jul 2002, Thomas Lockhart wrote:
I've developed patches to be able to specify the location of the WAL
directory, with the default location being where it is now. The patches
define a new environment variable PGXLOG (a la PGDATA) and postmaster,
postgres, initdb and pg_ctl have
On Tue, 30 Jul 2002, Tom Lane wrote:
More generally, I do not like depending on postmaster environment
variables --- our experience with environment variables for database
locations has been uniformly bad
The existing secondary-location mechanism is horrible. Please do not
emulate
Marc G. Fournier [EMAIL PROTECTED] writes:
First and foremost in my mind ... how do you have two users in the system
with seperate passwords? ...
since as soon as there are two 'bruce' users, only one can have a password
Uh, we've *never* supported two bruce users ... users have always been
Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
First and foremost in my mind ... how do you have two users in the system
with seperate passwords? ...
since as soon as there are two 'bruce' users, only one can have a password
Uh, we've *never* supported two bruce users ...
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Uh, we've *never* supported two bruce users ...
He was being tricky by having different passwords for the same user on
each database, so one user couldn't get into the other database, even
though it was the same name.
But the system
Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
First and foremost in my mind ... how do you have two users in the system
with seperate passwords? ...
since as soon as there are two 'bruce' users, only one can have a password
Uh, we've *never* supported two bruce users ...
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Uh, we've *never* supported two bruce users ...
He was being tricky by having different passwords for the same user on
each database, so one user couldn't get into the other database, even
though it was the same
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Uh, we've *never* supported two bruce users ...
He was being tricky by having different passwords for the same user on
each database, so one user couldn't get into the other database, even
though it was the same
Tom Lane wrote:
Thomas Lockhart [EMAIL PROTECTED] writes:
I've developed patches to be able to specify the location of the WAL
directory, with the default location being where it is now. The patches
define a new environment variable PGXLOG (a la PGDATA) and postmaster,
postgres, initdb
On Tue, 30 Jul 2002, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
First and foremost in my mind ... how do you have two users in the system
with seperate passwords? ...
since as soon as there are two 'bruce' users, only one can have a password
Uh, we've *never* supported
On Tue, 30 Jul 2002, Bruce Momjian wrote:
Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
First and foremost in my mind ... how do you have two users in the system
with seperate passwords? ...
since as soon as there are two 'bruce' users, only one can have a password
On Tue, 30 Jul 2002, Bruce Momjian wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Uh, we've *never* supported two bruce users ...
He was being tricky by having different passwords for the same user on
each database, so one user couldn't get into
Marc G. Fournier wrote:
You seem to have done a nice job with the + and @ for 'maps' ... how about
third on that states that the map file has a username:password pair in it?
I do like how the pg_hba.conf has changed, just don't like the lose of
functionality :(
OK, but the only logic for
In my original statement_timeout code, if a query string had multiple
statements, I would time the statements individually. I have modified
it so it now times the entire string collectively.
Do people realize that if you pass a single string to the backend, it
makes the string into a single
On Tue, 30 Jul 2002, Bruce Momjian wrote:
Marc G. Fournier wrote:
You seem to have done a nice job with the + and @ for 'maps' ... how about
third on that states that the map file has a username:password pair in it?
I do like how the pg_hba.conf has changed, just don't like the lose of
I've developed patches to be able to specify the location of the WAL
directory, with the default location being where it is now. The patches
define a new environment variable PGXLOG (a la PGDATA) and postmaster,
postgres, initdb and pg_ctl have been taught to recognize a new command
75 matches
Mail list logo
