[HACKERS] ECPG, threading and pooling

2003-01-23 Thread Shridhar Daithankar[EMAIL PROTECTED]
Hi all, I would like to use ECPG as it is relatively easy to code. However my application is multithreaded and also uses connecion pools. I would like to know if ECPG is thread safe and I can use an arbitrary PGconn* object pulled from a connection pool. Do I need to use connection name? I

Re: Windows Build System was: [HACKERS] Win32 port patches

2003-01-23 Thread Darko Prenosil
On Wednesday 22 January 2003 20:47, [EMAIL PROTECTED] wrote: Firebird uses a set of Borland command line tools and Borland's make, which they give away as a free download. Even if you're compiling for Windows, the build process uses Borland's command line make. A batch build script copies

Re: [HACKERS] Terrible performance on wide selects

2003-01-23 Thread Hannu Krosing
Tom Lane kirjutas N, 23.01.2003 kell 02:18: Dann Corbit [EMAIL PROTECTED] writes: Why not waste a bit of memory and make the row buffer the maximum possible length? E.g. for varchar(2000) allocate 2000 characters + size element and point to the start of that thing. Surely you're not

Re: [HACKERS] Oracle rant

2003-01-23 Thread Curt Sampson
On Thu, 16 Jan 2003, Fred Zellinger wrote: With Oracle, you can screw around with files and tablespaces and extents and segments and partition striping and local and global indexing and block sizes and 400+ other tuning parameters to your heart's content. ... I am a control freak and I think

Re: [HACKERS] Survey results from the PostgreSQL portal page

2003-01-23 Thread Curt Sampson
On Sun, 19 Jan 2003, [ISO-8859-1] Hans-J$B|(Brgen Sch$Bv(Bnig wrote: (B (B + people measure postgresql by the speed of bulk imports (B (B This is a good point. I can complete agree. What we might need is (B something called "SQL Loader" or so. This may sound funny and it doesn't (B make

Re: [HACKERS] Call for objections: put back OIDs in CREATE TABLE

2003-01-23 Thread Curt Sampson
On Tue, 21 Jan 2003, Tom Lane wrote: We've gotten a couple of complaints now about the fact that 7.3 doesn't include an OID column in a table created via CREATE TABLE AS or SELECT INTO. Unless I hear objections, I'm going to revert it to including an OID, and back-patch the fix for 7.3.2 as

BAD sig (was: Re: [HACKERS] v7.3.1 psql against a v7.2.x database...)

2003-01-23 Thread Adrian 'Dagurashibanipal' von Bidder
The keep-annoying-everybody-until-it-really-works caompain gpg: armor header: Version: GnuPG v1.2.1 (FreeBSD) gpg: Signature made Mit 22 Jan 2003 18:43:21 CET using DSA key ID 8C3ABF0C gpg: BAD signature from Rod Taylor (Database Developer) [EMAIL PROTECTED] On Mit, 2003-01-22 at 18:43, Rod

Re: [PERFORM] [HACKERS] Terrible performance on wide selects

2003-01-23 Thread Hannu Krosing
Dann Corbit kirjutas N, 23.01.2003 kell 02:39: [snip] For the disk case, why not have the start of the record contain an array of offsets to the start of the data for each column? It would only be necessary to have a list for variable fields. So (for instance) if you have 12

Re: [HACKERS] Threads

2003-01-23 Thread Curt Sampson
On Sat, 4 Jan 2003, Christopher Kings-Lynne wrote: Also remember that in even well developed OS's like FreeBSD, all a process's threads will execute only on one CPU. I would say that that's not terribly well developed. Solaris will split a single processes' threads over multiple CPUs, and I

Re: [HACKERS] Call for objections: put back OIDs in CREATE TABLE AS/SELECT INTO

2003-01-23 Thread Tom Lane
Curt Sampson [EMAIL PROTECTED] writes: I object. I personally think we should be moving towards not using OIDs as the default behaviour, inasmuch as we can, for several reasons: All these objections are global in nature, not specific to CREATE TABLE AS. The argument that persuaded me to do

Re: [HACKERS] Threads

2003-01-23 Thread Steve Wampler
On Sat, 4 Jan 2003, Christopher Kings-Lynne wrote: Also remember that in even well developed OS's like FreeBSD, all a process's threads will execute only on one CPU. I doubt that - it certainly isn't the case on Linux and Solaris. A thread may *start* execution on the same CPU as it's

Re: [HACKERS] ECPG, threading and pooling

2003-01-23 Thread Shridhar Daithankar
On Thursday 23 January 2003 08:40 pm, you wrote: On Thu, Jan 23, 2003 at 02:40:33PM +0530, Shridhar Daithankar[EMAIL PROTECTED] wrote: I would like to know if ECPG is thread safe and I can use an arbitrary PGconn* object pulled from a connection pool. Not sure what you mean with this?

Re: [HACKERS] Options for growth

2003-01-23 Thread Curt Sampson
On Wed, 22 Jan 2003, Sean Chittenden wrote: By the way, I too wonder which supported OS platform would support over 4GB of memory on a PC.. Linux? I don't think there's any problem handling more than 4G memory in the system. On 32bit architectures, there's of course the 3G (I think)

Re: [HACKERS] Threads

2003-01-23 Thread Shridhar Daithankar
On Thursday 23 January 2003 08:42 pm, you wrote: On Sat, 4 Jan 2003, Christopher Kings-Lynne wrote: Also remember that in even well developed OS's like FreeBSD, all a process's threads will execute only on one CPU. I doubt that - it certainly isn't the case on Linux and Solaris. A thread

Re: [HACKERS] Call for objections: put back OIDs in CREATE TABLE AS/SELECT INTO

2003-01-23 Thread Ross J. Reedstrom
On Thu, Jan 23, 2003 at 10:03:28AM -0500, Tom Lane wrote: Curt Sampson [EMAIL PROTECTED] writes: I object. I personally think we should be moving towards not using OIDs as the default behaviour, inasmuch as we can, for several reasons: All these objections are global in nature, not

Re: [HACKERS] Call for objections: put back OIDs in CREATE TABLE

2003-01-23 Thread Curt Sampson
On Thu, 23 Jan 2003, Ross J. Reedstrom wrote: So in the longer term, we need to provide a replacement. Arguably, the primary key for a table is the right replacement, but we don't _require_ a pkey, so what to do in cases where this isn't one? You're stuck. SQL breaks with relational theory in

Re: [HACKERS] Threads

2003-01-23 Thread Greg Copeland
On Thu, 2003-01-23 at 09:12, Steve Wampler wrote: On Sat, 4 Jan 2003, Christopher Kings-Lynne wrote: Also remember that in even well developed OS's like FreeBSD, all a process's threads will execute only on one CPU. I doubt that - it certainly isn't the case on Linux and Solaris. A

Re: [HACKERS] createlang failed!

2003-01-23 Thread John Liu
Thanks, fixed. The problem was caused - there's a postgreSQL came with the Redhat server, but I tried to install one only used by a specific user, I set LD_LIBRARY_PATH in this user's profile. pg_config --pkglibdir points to the correct lib dir, but when I run createlang plpgsql template1 it keeps

Re: [HACKERS] Postgresql source

2003-01-23 Thread radha . manohar
Can you please tell me how can I download all the source codes for postgresql?? -Radha Manohar ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

Re: [HACKERS] ECPG, threading and pooling

2003-01-23 Thread Michael Meskes
On Thu, Jan 23, 2003 at 08:58:24PM +0530, Shridhar Daithankar wrote: Well, when using libpq, I create a pool of PGconn*. What pool I create with ecpg? Looking at ecpglib.h, it seems that I need to create a pool of char * Yes. You use it as EXEC SQL AT :connection_var SELECT ... That is

[HACKERS] On Commit Triggers

2003-01-23 Thread Antonio Scotti
I am using PostgreSQL for some application and I've come in the need of a Before Commit and an After Commit trigger. PostgreSQL currently doesn't support them and I am wondering if it will ever be possible for developers to add them. Antonio Scotti ---(end of

Re: [HACKERS] Threads

2003-01-23 Thread mlw
Greg Copeland wrote: On Thu, 2003-01-23 at 09:12, Steve Wampler wrote: On Sat, 4 Jan 2003, Christopher Kings-Lynne wrote: Also remember that in even well developed OS's like FreeBSD, all a process's threads will execute only on one CPU. I doubt that

[HACKERS] Cast and Schemas don't work as expected

2003-01-23 Thread Eduardo Stern
The CREATE CAST command is't supporting schemas on the type parameters. A query such as: CREATE CAST (public.lo AS oid) WITH FUNCTION newoid (public.lo) AS IMPLICIT; Gives an error. And the problem happens when you create a CAST without the schema notation, and then try to do a dump/restore

[HACKERS] New buildin function

2003-01-23 Thread Olleg Samoylov
Hi! What about adding new function: pg_uid() pg_session_uid() as reference to internal function GetUserId() and GetSessionUserId(). These can help useful, for instance in row based securety. -- Olleg Samoylov ---(end of broadcast)--- TIP 3: if

Re: [HACKERS] Release Scheduales: 7.2.4 7.3.2

2003-01-23 Thread Marc G. Fournier
On Wed, 22 Jan 2003, Robert Treat wrote: On Wed, 2003-01-22 at 14:23, Marc G. Fournier wrote: If anyone has any 'last minute' issues they would like to see in either, please speak now or forever hold your peace :) Can someone post a changelog for these releases? Also what tags will be

Re: [HACKERS] Cast and Schemas don't work as expected

2003-01-23 Thread Christopher Kings-Lynne
That's probably because CASTS are database-wide and are not in schemas. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Eduardo Stern Sent: Sunday, 19 January 2003 11:07 PM To: [EMAIL PROTECTED] Subject: [HACKERS] Cast and Schemas don't work

Re: [HACKERS] New buildin function

2003-01-23 Thread Rod Taylor
On Wed, 2003-01-22 at 08:09, Olleg Samoylov wrote: Hi! What about adding new function: pg_uid() pg_session_uid() as reference to internal function GetUserId() and GetSessionUserId(). These can help useful, for instance in row based securety. Do CURRENT_USER and SESSION_USER not give

Re: [HACKERS] Cast and Schemas don't work as expected

2003-01-23 Thread Tom Lane
Eduardo Stern [EMAIL PROTECTED] writes: The CREATE CAST command is't supporting schemas on the type parameters. Yah. Are you enough of a yacc wizard to fix the reduce/reduce conflicts that arise when GenericType is made to include qualified names? I spent a couple days beating on that, without

Re: [HACKERS] Release Scheduales: 7.2.4 7.3.2

2003-01-23 Thread Justin Clift
Marc G. Fournier wrote: On Wed, 22 Jan 2003, Robert Treat wrote: On Wed, 2003-01-22 at 14:23, Marc G. Fournier wrote: If anyone has any 'last minute' issues they would like to see in either, please speak now or forever hold your peace :) Can someone post a changelog for these releases?

Re: [HACKERS] Release Scheduales: 7.2.4 7.3.2

2003-01-23 Thread Tom Lane
Justin Clift [EMAIL PROTECTED] writes: Have we determined that Tom's patch (the one that Josh wrote up) is indeed necessary? Necessary or not, it's in ;-) regards, tom lane ---(end of broadcast)--- TIP 6: Have you

Re: [HACKERS] [PATCH] psql visibility clarification patch

2003-01-23 Thread Tom Lane
D. Hageman [EMAIL PROTECTED] writes: The goal of this patch is a solution to the issue that I found concerning table visibility. The problem with the way psql currently lists tables in a database is that it limits it to only the tables currently in the search path. That's the intended

Re: [HACKERS] Options for growth

2003-01-23 Thread Hannu Krosing
Curt Sampson kirjutas N, 23.01.2003 kell 17:42: If the OS can handle the scheduling (which, last I checked, Linux couldn't, When did you do your checking ? (just curious, not to start a flame war ;) at least not without patches), eight or sixteen CPUs will be fine. cjs -- Hannu Krosing

Re: [HACKERS] Terrible performance on wide selects

2003-01-23 Thread Hannu Krosing
Dann Corbit kirjutas N, 23.01.2003 kell 02:22: [snip] So (for instance) if you have 12 variable fields, you would store 12 integers at the start of the record. Additionally, you could implicitly size the integers from the properties of the column. A varchar(255) would only need an

Re: [HACKERS] Foreign key wierdness

2003-01-23 Thread Hannu Krosing
Tom Lane kirjutas K, 22.01.2003 kell 22:30: Didier Moens [EMAIL PROTECTED] writes: I did some extensive testing using PostgreSQL 7.3.1 (logs and results available upon request), and the massive slowdown is NOT related to qualified tablename syntax or (lack of) VACUUM ANALYZE, but to the

Re: [HACKERS] Call for objections: put back OIDs in CREATE TABLE

2003-01-23 Thread Hannu Krosing
Curt Sampson kirjutas N, 23.01.2003 kell 13:34: On Tue, 21 Jan 2003, Tom Lane wrote: We've gotten a couple of complaints now about the fact that 7.3 doesn't include an OID column in a table created via CREATE TABLE AS or SELECT INTO. Unless I hear objections, I'm going to revert it to

Re: [HACKERS] Options for growth

2003-01-23 Thread Curt Sampson
On Fri, 23 Jan 2003, Hannu Krosing wrote: Curt Sampson kirjutas N, 23.01.2003 kell 17:42: If the OS can handle the scheduling (which, last I checked, Linux couldn't, When did you do your checking ? (just curious, not to start a flame war ;) This was perhaps a year or so ago. IBM had some

Re: [HACKERS] Call for objections: put back OIDs in CREATE TABLE

2003-01-23 Thread Curt Sampson
On Fri, 23 Jan 2003, Hannu Krosing wrote: 1. [OIDs are] not a relational concept. so are other system tuples (cid, tid, tableiod, ...). But there's a key difference here; nobody's advertising these others as any sort of row identifier: i.e., a candidate key. And besides, I wouldn't object at

Re: [HACKERS] Terrible performance on wide selects

2003-01-23 Thread Hannu Krosing
Tom Lane kirjutas N, 23.01.2003 kell 02:04: Dann Corbit [EMAIL PROTECTED] writes: Maybe I don't really understand the problem, but it seems simple enough to do it once for the whole query. We already do cache column offsets when they are fixed. The code that's the problem executes when

Re: [HACKERS] Terrible performance on wide selects

2003-01-23 Thread Hannu Krosing
Hannu Krosing kirjutas N, 23.01.2003 kell 12:11: make the pointer array incrementally for O(N) performance: i.e. for tuple with 100 cols, allocate an array of 100 pointers, plus keep count of how many are actually valid, Additionally, this should also make repeted determining of NULL fields

Re: [HACKERS] Terrible performance on wide selects

2003-01-23 Thread Daniel Kalchev
Hannu Krosing said: Tom Lane kirjutas N, 23.01.2003 kell 02:04: We already do cache column offsets when they are fixed. The code that's the problem executes when there's a variable-width column in the table --- which means that all columns to its right are not at fixed offsets, and

Re: [HACKERS] Call for objections: put back OIDs in CREATE TABLE

2003-01-23 Thread D'Arcy J.M. Cain
On Thursday 23 January 2003 06:34, Curt Sampson wrote: The ideal sitaution for me would be to have WITHOUT OIDS be the default for all table creations, and but of course allow WITH OIDS for backward Why not make it a configuration option? I can actually think of a third behaviour that would

Re: [HACKERS] Terrible performance on wide selects

2003-01-23 Thread Tom Lane
Hannu Krosing [EMAIL PROTECTED] writes: i.e. for tuple with 100 cols, allocate an array of 100 pointers, plus keep count of how many are actually valid, Additionally, this should also make repeted determining of NULL fields faster - just put a NULL-pointer in and voila - no more bit-shifting

Re: [PERFORM] [HACKERS] Terrible performance on wide selects

2003-01-23 Thread Tom Lane
Hannu Krosing [EMAIL PROTECTED] writes: as tuple (int,int,int,varchar,varchar) which is currently stored as (intdata1, intdata2, intdata3, (len4, vardata4), (len5,vardata5)) should be rewritten on storage to (ptr4,ptr5),(intdata1, intdata2, intdata3, vardata4,vardata5) I do not see that

Re: [HACKERS] Terrible performance on wide selects

2003-01-23 Thread Tom Lane
Daniel Kalchev [EMAIL PROTECTED] writes: Does this mean, that constructing tables where fixed length fields are 'before' variable lenght fields and 'possibly null' fields might increase performance? There'd have to be no nulls, period, to get any useful performance difference --- but yes, in

Re: [HACKERS] Options for growth

2003-01-23 Thread Curt Sampson
On Thu, 16 Jan 2003, D'Arcy J.M. Cain wrote: Due to the fact that we are growing out of our current system (PostgreSQL on PCs) we are looking for ways to expand and one of the suggestions has been to toss PostgreSQL in favour of Oracle with Remote Access Cluster (RAC) software. The theory is

Re: [PERFORM] [HACKERS] Terrible performance on wide selects

2003-01-23 Thread Curt Sampson
On Thu, 23 Jan 2003, Daniel Kalchev wrote: Does this mean, that constructing tables where fixed length fields are 'before' variable lenght fields and 'possibly null' fields might increase performance? This, I believe, is why DB2 always puts (in physical storage) all of the fixed-length fields

Re: [HACKERS] Options for growth

2003-01-23 Thread scott.marlowe
On 23 Jan 2003, Hannu Krosing wrote: Curt Sampson kirjutas N, 23.01.2003 kell 17:42: If the OS can handle the scheduling (which, last I checked, Linux couldn't, When did you do your checking ? (just curious, not to start a flame war ;) at least not without patches), eight or sixteen

Re: [PATCHES] targetlist functions part 1 (was [HACKERS] targetlist

2003-01-23 Thread Peter Eisentraut
I wrote: The SQL 200x draft defines a new clause TABLE ( collection value expression ) as a possible table primary, where the collection value expression is required to be a function call. At the end this just boils down to UNNEST, though. UNNEST is defined in terms of a hairy recursive

Re: [HACKERS] [pgsql-advocacy] Translation of the PostgreSQL manuals to

2003-01-23 Thread Alberto Caso
El vie, 17-01-2003 a las 03:03, Justin Clift escribió: Hi everyone, Christian Kuroki [EMAIL PROTECTED] is a senior member of a team that is translating the PostgreSQL manuals to Spanish. [...] Does anyone out here who knows/writes Spanish have a bit of time to assist them with

Re: [HACKERS] [GENERAL] Translation of the PostgreSQL manuals to Spanish is under way

2003-01-23 Thread Claudio Lapidus
Hello Justin, Perhaps I'll be able to offer some help. I'm a fair translator, IMHO. Christian, please contact me directly to see what can be done. regards, cl. Enviado por: [EMAIL PROTECTED] Destinatarios: PostgreSQL Advocacy Mailing List [EMAIL PROTECTED], PostgreSQL

Re: [HACKERS] Foreign key wierdness

2003-01-23 Thread Didier Moens
Dear Tom, Dave, Tom Lane wrote: Ah-hah, and I'll bet that the column being linked to this one by the foreign key constraint is still an integer? It sure is ; being a PostgreSQL novice (BTW : many thanks to the whole of the PG development team for such an excellent product), I got on this

Re: [HACKERS] Foreign key wierdness

2003-01-23 Thread Didier Moens
Hi all, Dave Page wrote: If you really think the schema qualification has something to do with it, try issuing the ADD FOREIGN KEY command manually in psql, with and without schema name. Well to be honest I'm having a hard time believing it, but having looked at this in some depth, it's

Re: [HACKERS] Windows Build System

2003-01-23 Thread Curtis Faith
Curtis Faith wrote: The Visual C++ Workspaces and Projects files are actually text files that have a defined format. I don't think the format is published but it looks pretty easy to figure out. Hannu Krosing wrote: will probably change between releases Even if the format changes, the

Re: [HACKERS] Foreign key wierdness

2003-01-23 Thread Didier Moens
Dave Page wrote: From what Tom has said in his reponse, I think the answer for you Didier is to remap your integer columns to int8 instead of int4 and see what happens. When I get a couple of minutes I will look at putting a Serials as... Option in the type map. Thanks Dave, for all of your

Re: [HACKERS] New buildin function

2003-01-23 Thread Peter Eisentraut
Olleg Samoylov writes: What about adding new function: pg_uid() pg_session_uid() as reference to internal function GetUserId() and GetSessionUserId(). CURRENT_USER, SESSION_USER -- Peter Eisentraut [EMAIL PROTECTED] ---(end of

Re: [HACKERS] C++ coding assistance request for a

2003-01-23 Thread Greg Copeland
On Wed, 2003-01-22 at 23:40, Justin Clift wrote: Justin Clift wrote: Greg Copeland wrote: Have you tried IBM's OSS visualization package yet? Sorry, I don't seem to recall the name of the tool off the top of my head (Data Explorer??) but it uses OpenGL (IIRC) and is said to be able to

[HACKERS] Odd subselect in target list behavior WRT aggregates

2003-01-23 Thread Mike Mascari
Hello. I have some code which generates subselects in the target list of a query and then aggregates the results. The code allows the user to determine the attributes of the aggregation. If the user chooses to aggregate on the same value twice, I get the Sub-SELECT error. If the user chooses a