Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-07-18 Thread Gavin Sherry
On Fri, 18 Jul 2003, Bruce Momjian wrote: > Tom Lane wrote: > > [EMAIL PROTECTED] writes: > > > I disagree. Just as you can have multiple schemas within one database > > > you can have multiple tablespaces within one database. > > > > > And the tablespace is irrelevant as far as specifying an

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-07-18 Thread Rod Taylor
> Another good reason for per-database directories under the tablespace is > to prevent directories from containing too many files. Actually, I would take that as an reason not to have database directories. If the number of files becomes a concern, we would need some kind of a hashing algorithm t

Re: [HACKERS] commiters log

2003-07-18 Thread Oleg Bartunov
On Fri, 18 Jul 2003, The Hermit Hacker wrote: > > posted and shouldn't be delay'd in the future ... > Thanks, Marc. Oleg > On Fri, 18 Jul 2003, Tom Lane wrote: > > > Oleg Bartunov <[EMAIL PROTECTED]> writes: > > > today we've commited bug fix in ltree code to current CVS, but I don't se

Re: [HACKERS] [GENERAL] Physical Database Configuration

2003-07-18 Thread Bruce Momjian
Tom Lane wrote: > [EMAIL PROTECTED] writes: > > I disagree. Just as you can have multiple schemas within one database > > you can have multiple tablespaces within one database. > > > And the tablespace is irrelevant as far as specifying an object is concerned. > > A fully qualified object would

Re: [HACKERS] commiters log

2003-07-18 Thread The Hermit Hacker
posted and shouldn't be delay'd in the future ... On Fri, 18 Jul 2003, Tom Lane wrote: > Oleg Bartunov <[EMAIL PROTECTED]> writes: > > today we've commited bug fix in ltree code to current CVS, but I don't see > > any notices in COMMITERS mailing list. Do we need to so something > > special ? >

Re: [HACKERS] Archives

2003-07-18 Thread The Hermit Hacker
On Wed, 16 Jul 2003, Alvaro Herrera wrote: > On Wed, Jul 16, 2003 at 01:57:41PM -0500, Thomas Swan wrote: > > Does anyone have recent archives of the pgsql-hackers list in mbx or > > flat file format? > > > > I know that I can search through the website or through other > > interfaces, but I would

Re: [HACKERS] Patches List

2003-07-18 Thread The Hermit Hacker
On Thu, 17 Jul 2003, Robert Treat wrote: > On Thu, 2003-07-17 at 14:11, Rod Taylor wrote: > > On Wed, 2003-07-16 at 21:16, Tom Lane wrote: > > > Larry Rosenman <[EMAIL PROTECTED]> writes: > > > > Is the patches list working? > > > > > > I saw something come through yesterday from Rod. > > > > Whic

Re: [HACKERS] Patches List

2003-07-18 Thread The Hermit Hacker
Got stuck with: A MIME header is too long (353 > 128) going through postings now ... On Wed, 16 Jul 2003, Larry Rosenman wrote: > Yes I am subscribed. > > I also sent it to you directly seeing as if it was slow. > > LER > > > --On Wednesday, July 16, 2003 17:16:55 -0400 Tom Lane <[EMAIL PROTEC

Re: [HACKERS] dblink_ora - a first shot on Oracle ...

2003-07-18 Thread Bruce Momjian
Joe, I can do the configure detection of the Oracle library needed for /contrib. I don't think we follow the beta freeze as much for /contrib stuff, but this particular /contrib is more integrated into the main system than most. If you want to merge it in during the next month, I can do the conf

Re: [HACKERS] commiters log

2003-07-18 Thread Tom Lane
Oleg Bartunov <[EMAIL PROTECTED]> writes: > today we've commited bug fix in ltree code to current CVS, but I don't see > any notices in COMMITERS mailing list. Do we need to so something > special ? Check with Marc when he gets back from vacation. He probably forgot to give you some permission or

Re: [HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-18 Thread Rod Taylor
On Fri, 2003-07-18 at 19:46, Paulo Scardine wrote: > My boss is asking for something like Oracle's "SELECT FOR UPDATE NOWAIT". > > Is there any such feature? If no, should I look forward into implementing > this? Any advice? Lookup STATEMENT_TIMEOUT and set it to a very short time. signature.as

Re: [pgsql-advocacy] [HACKERS] [GENERAL] Postgresql & AMD x86-64

2003-07-18 Thread Manfred Spraul
Bruce Momjian wrote: if test "$enable_debug" = yes && test "$ac_cv_prog_cc_g" = yes; then CFLAGS="$CFLAGS -g" fi + + /* Compile AMD Opteron using gcc in 64-bit mode */ + if test "$GCC" = yes; then + case $host in + ia64-*) CFLAGS="$CFLAGS -m64" +LDFLAGS="$LDFLAGS -melf_x86_64"

[HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-18 Thread Paulo Scardine
My boss is asking for something like Oracle's "SELECT FOR UPDATE NOWAIT". Is there any such feature? If no, should I look forward into implementing this? Any advice? Thank you, -- Paulo Scardine --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com

[HACKERS] commiters log

2003-07-18 Thread Oleg Bartunov
Hi there, today we've commited bug fix in ltree code to current CVS, but I don't see any notices in COMMITERS mailing list. Do we need to so something special ? Regards, Oleg _ Oleg Bartunov, sci.researcher, host

Re: [HACKERS] CREATE TYPE

2003-07-18 Thread Mike Aubury
OK - i've got the basic input/output working now - but how to I do the extent bit ? eg. allow : create table ( something a4gl_datime(15) ) On Friday 18 July 2003 6:53 pm, [EMAIL PROTECTED] wrote: > Programmers Guide , Chap 10 > http://www.postgresql.org/docs/7.3/static/xtypes.html > > c

[HACKERS] Exception table ...

2003-07-18 Thread Hans-Jürgen Schönig
I have just seen a nice feature provided by DB2 which seems very useful to me. When importing huge amounts of data (dozens of gigs) with the help of COPY errors might occur from time to time (especially when migrating). The problem with COPY is that it stops after the first error. So if the fir

Re: [pgsql-advocacy] [HACKERS] [GENERAL] Postgresql & AMD x86-64

2003-07-18 Thread Bruce Momjian
The following patch automatically enables 64-bit mode on AMD opteron. We already had spinlock support for it, but I added some comments. The big question is whether all the operating systems running gcc on Opteron support the 64-bit flags, and if we want to enable them by default on Opteron. If

Re: [HACKERS] plpgsql strangeness with select into

2003-07-18 Thread Robert Treat
On Fri, 2003-07-18 at 11:24, Reinoud van Leeuwen wrote: > I'm debugging a trigger in plpgsql and for some reason or the "select > into " does not seem to work. Here is an unaltered snippet of my > trigger code: > >raise notice ''this id : %'',NEW.id; > >select into i_

Re: [HACKERS] CREATE TYPE

2003-07-18 Thread mallah
Programmers Guide , Chap 10 http://www.postgresql.org/docs/7.3/static/xtypes.html contrib/isbn_issn also provides an implementation example. regds mallah. > Can someone point me at some detailed instructions for creating new > datatypes.. > > I've found quite a few web pages that mention it (in

[HACKERS] CREATE TYPE

2003-07-18 Thread Mike Aubury
Can someone point me at some detailed instructions for creating new datatypes.. I've found quite a few web pages that mention it (in passing) and give brief examples - but nothing much I can actually work with for my purposes.. Ideally I'd like to use C as the language and the datatype will nee

[HACKERS] Another TODO for PL/pgSQL -- Dynamic colums

2003-07-18 Thread Josh Berkus
Developers, While I realize that we already have a number of TODOs on the list for PL/pgSQL which nobody is working on, I'd like to propose one more. That way, when someday somebody takes this on, they'll have a full list of feature requests. This one gets requested about once per month on th

[HACKERS] plpgsql strangeness with select into

2003-07-18 Thread Reinoud van Leeuwen
I'm debugging a trigger in plpgsql and for some reason or the "select into " does not seem to work. Here is an unaltered snippet of my trigger code: raise notice ''this id : %'',NEW.id; select into i_hierarchy_id hierarchy_id from link_def LD,

Re: [HACKERS] pgsql-server/src/backend/commands comment.c

2003-07-18 Thread Rod Taylor
> For COMMENT ON DATABASE where database name is unknown or not the current > database, emit a WARNING and do nothing, rather than raising ERROR. > Per recent discussion in which we concluded this is the best way to deal > with database dumps that are reloaded into a databas