Re: [GENERAL] Query to get column-names in table via PG tables?

2008-01-14 Thread Ken Johanson
I am looking for expertise on how to program the equivalent to this query, but using the pg_catalog tables, which I understand have fewer security restrictions than information_schema in some cases: SELECT column_name FROM information_schema.columns WHERE table_catalog=? AND table_schema=? AND ta

Re: [GENERAL] Locking & concurrency - best practices

2008-01-14 Thread Adam Rich
> Advisory locks would work here (better that than table lock), but I > don't think that's the right approach. Transaction 2 should simply do > a > select * from parent_tbl > where id=1 for update; > > at the start of the transaction. That's actually what I'm doing (just forgot to include it in

Re: [GENERAL] Locking & concurrency - best practices

2008-01-14 Thread Merlin Moncure
On Jan 14, 2008 5:57 PM, Adam Rich <[EMAIL PROTECTED]> wrote: > > > > From what I can tell, this kind of roll-your-own application level > > locking system is exactly what advisory locks are for. Search the > > archives for the last couple of weeks as I remember someone posting > > some really he

Re: [GENERAL] Locking & concurrency - best practices

2008-01-14 Thread Merlin Moncure
On Jan 14, 2008 4:31 PM, Adam Rich <[EMAIL PROTECTED]> wrote: > > You should be able to do "select for update" on both parent and child > > records and get the effect you desire. > > > > I don't think that will work. Let me demonstrate: > (this is simplified, but sufficient to make my point) > > -

Re: [GENERAL] Satisfactory Query Time

2008-01-14 Thread Merlin Moncure
On Jan 13, 2008 4:55 PM, x asasaxax <[EMAIL PROTECTED]> wrote: > Hi, > >I have a query that takes 0.450 ms. Its a xml query. Is that a good time > for a query? If a have multiple connections on the database, will this time > makes my db slow? How much time is good for a xml query? You have pro

Re: [GENERAL] What pg_restore does to a non-empty target database

2008-01-14 Thread Ken Winter
Based on Tom Lane's response, here is version 2 of my attempt to document what pg_restore does to a target database that already contains objects. Version 2 has been limited to the case where pg_dump was run with the --column-inserts option and pg_restore is run with the --clean option. Also, w

[GENERAL] Registration for PostgreSQL Conference East now open

2008-01-14 Thread Joshua D. Drake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Registration for PostgreSQL Conference: East is now open. For those who haven't seen the emails, the conference is taking place at University of Maryland in College Park. This location is about 10 minutes from Washington D.C. The dates of the c

Re: [GENERAL] Locking & concurrency - best practices

2008-01-14 Thread Erik Jones
On Jan 14, 2008, at 4:57 PM, Adam Rich wrote: From what I can tell, this kind of roll-your-own application level locking system is exactly what advisory locks are for. Search the archives for the last couple of weeks as I remember someone posting some really helpful functions to assist in us

Re: [GENERAL] Locking & concurrency - best practices

2008-01-14 Thread Adam Rich
> > From what I can tell, this kind of roll-your-own application level > locking system is exactly what advisory locks are for. Search the > archives for the last couple of weeks as I remember someone posting > some really helpful functions to assist in using advisory locks. > > Erik Jones Yes

Re: [GENERAL] Locking & concurrency - best practices

2008-01-14 Thread Erik Jones
On Jan 14, 2008, at 3:54 PM, andy wrote: In our program we wrote the locking into the program, and created a modulelock table like: create table moduelock( userid int, module int, primary key (userid, module) ) The program then locks things before it uses them... but we also have pr

Re: [GENERAL] Locking & concurrency - best practices

2008-01-14 Thread andy
Adam Rich wrote: I have a "parent_tbl" and dozens of data tables, with foreign keys referencing the PK of "parent_tbl" (one-to-many). There are 100+ users accessing the application, usually (but not always) each user is working on a different record in parent_tbl. (this would seem like a pret

Re: [GENERAL] Locking & concurrency - best practices

2008-01-14 Thread Scott Marlowe
On Jan 14, 2008 3:31 PM, Adam Rich <[EMAIL PROTECTED]> wrote: > > You should be able to do "select for update" on both parent and child > > records and get the effect you desire. > > > > I don't think that will work. Let me demonstrate: > (this is simplified, but sufficient to make my point) > > -

Re: [GENERAL] Locking & concurrency - best practices

2008-01-14 Thread Adam Rich
> You should be able to do "select for update" on both parent and child > records and get the effect you desire. > I don't think that will work. Let me demonstrate: (this is simplified, but sufficient to make my point) -- Connection 1 -- begin trans; select * from parent_tbl where id=1 for upda

Re: [GENERAL] Locking & concurrency - best practices

2008-01-14 Thread Scott Marlowe
On Jan 14, 2008 2:43 PM, Adam Rich <[EMAIL PROTECTED]> wrote: > > I have a "parent_tbl" and dozens of data tables, with foreign keys > referencing the PK of "parent_tbl" (one-to-many). There are 100+ > users accessing the application, usually (but not always) each user > is working on a different

Re: [GENERAL] Forgot to dump old data before re-installing machine

2008-01-14 Thread Gurjeet Singh
And also remember to use the same version of Postgres as the previous installation... It might be helpful to post the tail of your server's log ahen it fails. Best Regards, On Jan 14, 2008 7:58 AM, Tom Lane <[EMAIL PROTECTED]> wrote: > Stefan Schwarzer <[EMAIL PROTECTED]> writes: > > I re-insta

[GENERAL] Locking & concurrency - best practices

2008-01-14 Thread Adam Rich
I have a "parent_tbl" and dozens of data tables, with foreign keys referencing the PK of "parent_tbl" (one-to-many). There are 100+ users accessing the application, usually (but not always) each user is working on a different record in parent_tbl. (this would seem like a pretty standard scena

Re: [GENERAL] oddly slow query

2008-01-14 Thread Tom Lane
Jessi Berkelhammer <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> For some reason it's estimating only one row out of the >> clinical_reg_current view will satisfy the >> tier_program(benefit_type_code) = 'SAGE' constraint. My math was off the other day --- actually, that's exactly what you'd ex

Re: [GENERAL] oddly slow query

2008-01-14 Thread Jessi Berkelhammer
Hello. Thanks for the help. Tom Lane wrote: Jessi Berkelhammer <[EMAIL PROTECTED]> writes: Here are the 3 EXPLAIN ANALYZE commands followed by the output: Well, here's the problem: Join Filter: (clinical_reg_current.client_id = client.client_id) -> Subquery Scan clinic

Re: [GENERAL] tcp_keepalives_idle ignored

2008-01-14 Thread henry
On Mon, January 14, 2008 12:49 pm, henry wrote: > WRT the origional question: why is tcp_keepalives_idle being ignored > (whether with SET or in postgresql.conf)? - ie, SHOW ALL says it's 0 no > matter what I do. A quick follow-on with more info to my own post. The culprit in my case was a loc

[GENERAL] Members-choice award at LinuxQuestions.org

2008-01-14 Thread Andrej Ricnik-Bay
Hi Guys, Apologies for the cross-post, I already posted this in advocacy a few days ago, and am hoping for a slightly better exposure here. Over at http://www.linuxquestions.org a members-choice award for 2007 is currently going on. Every year I see a great influx of people signing up solely for

Re: [GENERAL] Online Oracle to Postgresql data migration

2008-01-14 Thread Josh Harrison
Thanks On Jan 12, 2008 9:19 AM, David Fetter <[EMAIL PROTECTED]> wrote: > On Fri, Jan 11, 2008 at 01:02:01PM -0500, Josh Harrison wrote: > > Hi > > We have an Oracle production database with some terbytes of data. We > > wanted to migrate that to Postgresql (rigt now...a test database and > > not

Re: [GENERAL] tcp_keepalives_idle ignored

2008-01-14 Thread henry
On Mon, January 14, 2008 5:46 pm, Tom Lane wrote: >> So,... this appears to be dblink related after all. I'll be trying >> explicit open/exec/close. Weird that dblink_exec in a trigger doesn't >> release resources. > > Hmm, this is the transient-connection form of dblink? If so, that would > be

Re: [GENERAL] Forgot to dump old data before re-installing machine

2008-01-14 Thread Tom Lane
Stefan Schwarzer <[EMAIL PROTECTED]> writes: > I re-installed my machine and "forgot" to dump my database(s). I > naturally still have the whole database folders. For the moment I > installed the "old" postgres version (8.1) to be able to read my data. > But how can I read them? It seems that

Re: [GENERAL] ECPG problem with 8.3

2008-01-14 Thread Tom Lane
Peter Wilson <[EMAIL PROTECTED]> writes: > Michael Meskes wrote: >> Yes. ECPG move to the latest backend protocol version to be able to >> prepare statements correctly. However, with this protocol my own >> addition to the standard, namely a variable as fetch count, is not >> supported anymore. But

Re: [GENERAL] tcp_keepalives_idle ignored

2008-01-14 Thread Tom Lane
"henry" <[EMAIL PROTECTED]> writes: > The culprit in my case was a local trigger firing on INSERTs using > dblink_exec() without 'host=127.0.0.1'. Bad news though, even _with_ > 'host=127.0.0.1' the connections do not idle timeout. They just hang > around waiting for the rapture. > So,... this a

Re: [GENERAL] tcp_keepalives_idle ignored

2008-01-14 Thread Tom Lane
"henry" <[EMAIL PROTECTED]> writes: > WRT the origional question: why is tcp_keepalives_idle being ignored > (whether with SET or in postgresql.conf)? - ie, SHOW ALL says it's 0 no > matter what I do. I think you're looking at it in a session that's connecting over a Unix socket. You need to be

Re: [GENERAL] ERROR: shared buffer hash table corrupted

2008-01-14 Thread Tom Lane
Ashish Karalkar <[EMAIL PROTECTED]> writes: > Hello list members,I hav a table with 140M rows. While I am > trying to select the count from the tableI am getting following > errorERROR:  shared buffer hash table corruptedCan > anybody please suggest me wht had gone wrong and how to fix > it?Pos

Re: [GENERAL] ECPG problem with 8.3

2008-01-14 Thread Shelby Cain
- Original Message > From: Peter Wilson <[EMAIL PROTECTED]> > To: Michael Meskes <[EMAIL PROTECTED]>; pgsql-general@postgresql.org > Sent: Monday, January 14, 2008 8:41:12 AM > Subject: Re: [GENERAL] ECPG problem with 8.3 > > Fetch with a variable seems to be almost the only useful way

Re: [GENERAL] ECPG problem with 8.3

2008-01-14 Thread Peter Wilson
Michael Meskes wrote: On Sun, Jan 13, 2008 at 03:01:04PM +, Peter Wilson wrote: that fixes that problem. My build now gets further, but I get an error and a seg-fault later in the build. Whow, you're really stress testing it. Thanks a lot! This is what we need. I have to say I didn't wri

[GENERAL] Forgot to dump old data before re-installing machine

2008-01-14 Thread Stefan Schwarzer
Hi there, I re-installed my machine and "forgot" to dump my database(s). I naturally still have the whole database folders. For the moment I installed the "old" postgres version (8.1) to be able to read my data. But how can I read them? It seems that it doesn't work that I just overwrite

Re: [GENERAL] tcp_keepalives_idle ignored

2008-01-14 Thread henry
On Sun, January 13, 2008 6:53 pm, henry wrote: > On Sun, January 13, 2008 7:25 pm, Tom Lane wrote: >> Martijn van Oosterhout <[EMAIL PROTECTED]> writes: >>> On Sun, Jan 13, 2008 at 08:40:34AM +0200, henry wrote: lsof doesn't tell me what's talking to PG through /tmp/.s.PGSQL.5432 either.

Re: [GENERAL] Installation problem: failed to initialize lc_messages to ""

2008-01-14 Thread Stefan Schwarzer
I'm wondering if some of those files are missing, or the symlinks are dangling, on yours. Hmmm. here is what I have. Looks pretty similar Running out of easy answers, aren't we :-( The next thing I can think of is to run initdb under "ktrace -i" and compare the results with a worki

[GENERAL] ERROR: shared buffer hash table corrupted

2008-01-14 Thread Ashish Karalkar
Hello list members,I hav a table with 140M rows. While I am trying to select the count from the tableI am getting following errorERROR:  shared buffer hash table corruptedCan anybody please suggest me wht had gone wrong and how to fix it?PostgreSQL 8.2.4OS:Suse 10.3With RegardsAshish... Sa

Re: [GENERAL] ECPG problem with 8.3

2008-01-14 Thread Michael Meskes
On Sun, Jan 13, 2008 at 03:01:04PM +, Peter Wilson wrote: > that fixes that problem. My build now gets further, but I get an error > and a seg-fault later in the build. Whow, you're really stress testing it. Thanks a lot! This is what we need. > Apart from the seg-fault, is there any particu