Re: [HACKERS] Call for platforms

2001-03-20 Thread Tatsuo Ishii
> > mklinux PPC750 7.0 2000-04-13, Tatsuo Ishii > > I got core dump while running the parallel regression test of beta6. > Will look at... > -- > Tatsuo Ishii VACUUM; ! FATAL 2: ZeroFill(logfile 0 seg 1) failed: No such file or directory ! pqReadData() -- backend closed the channel unexpe

RE: [HACKERS] libpqeasy cursor error after multiple calls

2001-03-20 Thread Christopher Kings-Lynne
I don't know but it may be that you're trying to insert a number larger than maxint? ie: 2147483648 ??? Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Justin Clift Sent: Tuesday, 20 March 2001 5:54 PM To: [EMAIL PROTECTED] Subject: [HACKERS] lib

Re: [HACKERS] Call for platforms

2001-03-20 Thread Adriaan Joubert
> Compaq Tru64 5.0 Alpha 7.0 2000-04-11, Andrew McMurry We've got 7.0.3 and 7.1b4 running on Compaq Tru64 4.0G Alpha Will do the regression test once RC1 is out. Adriaan ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [

Re: [HACKERS] Call for platforms

2001-03-20 Thread Tatsuo Ishii
> mklinux PPC750 7.0 2000-04-13, Tatsuo Ishii I got core dump while running the parallel regression test of beta6. Will look at... -- Tatsuo Ishii ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate sub

[HACKERS] PostgreSQL-JDBC driver

2001-03-20 Thread sourabh dixit
- Hi, I am trying to access PostGreSQL database running at the default port 5432 using JDBC. But the application is giving error "Cannot find suitable driver". I have included JDBC driver JAR file in my CLASSPATH and Class.forName("org.postgresql.Driver") is loading driver successfully. Ca

Re: [HACKERS] libpqeasy cursor error after multiple calls

2001-03-20 Thread Bruce Momjian
I am kind of stumped. Glad to see _someone_ is using libpgeasy. :-) I would be glad to run tests here if you can shoot over the code. > Hi all, > > I'm just wondering if this is an error on my part, or a bug. I have the > same trouble with PG 7.1beta6 and PG7.1 snapshot (March 8th) on Sola

Re: [HACKERS] pg_inherits: not found, but visible [IT GETS WORSE]

2001-03-20 Thread Tom Lane
Joel Burton <[EMAIL PROTECTED]> writes: > Yikes. It gets weirder. > Fixed the pg_inherits problem, went back to my Zoping, trying to optimize > some views, and during another run, get an error that trelclasspq, one of > my tables, couldn't open. > Trying this out in psql, I get the same error mess

[HACKERS] regression.diff wrong dir name

2001-03-20 Thread Justin Clift
Hi all, Something minor, but when you do a "make check" from the main source directory and it finishes, it mentions that the regression.diff file is in ./regression.diff It's really at src/test/regress/regression.diff, and although not hard to figure out (it's a carry-over from pre 7.1), it migh

[HACKERS] libpqeasy cursor error after multiple calls

2001-03-20 Thread Justin Clift
Hi all, I'm just wondering if this is an error on my part, or a bug. I have the same trouble with PG 7.1beta6 and PG7.1 snapshot (March 8th) on Solaris 8 INTEL, Solaris 8 SPARC and Linux Mandrake 7.2. When using the libpqeasy library in a C function, I have the following section of code : //

[HACKERS] Question

2001-03-20 Thread Manal S
Hi, I want to ask question: can i write my own concurrency control algorithm and apply it using postgresql? Thanks in advance Manal __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ ---

[HACKERS] Re: RPM building (was regression on RedHat)

2001-03-20 Thread Thomas Swan
At 3/20/2001 09:24 PM, Thomas Lockhart wrote: > > It's a good start to test with for the purposes for which I think you > want to > > test for. (and I'm an English teacher by night -- argh). > >:) > >Mandrake (as of 7.2) still does a brain-dead mix of "-O3" and >"-ffast-math", which is a risky a

Re: [HACKERS] Re: Final Call: RC1 about to go out the door ...

2001-03-20 Thread Dominic J. Eidson
On Wed, 21 Mar 2001, Thomas Lockhart wrote: > > > >> Linux/PPC (LinuxPPC 2000 Q4 distro tested here; 2.2.18 kernel I think) > > > > What processor? Tatsuo had tested on a 603... > > > It's a Powerbook G3 (FireWire model), but I'm not sure which chip is > > > inside (and Apple's spec sheet i

[HACKERS] Re: More on elog and error codes

2001-03-20 Thread Philip Warner
At 03:28 21/03/01 +, Thomas Lockhart wrote: >> Creating central message files/objects has the added advantage of a much >> simpler locale support - they're just resource files, and they're NOT >> embedded throughout the code. >> Finally, if you do want to have some kind of error classification

[HACKERS] Re: More on elog and error codes

2001-03-20 Thread Thomas Lockhart
> Creating central message files/objects has the added advantage of a much > simpler locale support - they're just resource files, and they're NOT > embedded throughout the code. > Finally, if you do want to have some kind of error classification beyond > the SQL code, it could be encoded in the e

Re: [HACKERS] Re: Final Call: RC1 about to go out the door ...

2001-03-20 Thread Tatsuo Ishii
> > Tatsuo, I have a separate listing for "mklinux" for the 7.0 release. Is > > that distro still valid and unique? Or is there a better way to > > represent the PPC options under Linux? > > mklinux is older Motorola 68k-based systems No. MkLinux runs on Power PC based system also. I believe the

[HACKERS] RPM building (was regression on RedHat)

2001-03-20 Thread Thomas Lockhart
> It's a good start to test with for the purposes for which I think you want to > test for. (and I'm an English teacher by night -- argh). :) Mandrake (as of 7.2) still does a brain-dead mix of "-O3" and "-ffast-math", which is a risky and unnecessary combination according to the gcc folks (and

[HACKERS] Re: Final Call: RC1 about to go out the door ...

2001-03-20 Thread Tatsuo Ishii
> Tatsuo, I have a separate listing for "mklinux" for the 7.0 release. Is > that distro still valid and unique? Or is there a better way to > represent the PPC options under Linux? I think MkLinux is completely different from Linux/PPC. Will test RC1 on my MkLiux box soon... -- Tatsuo Ishii

[HACKERS] Re: PostgreSQL JDBC Unicode Support

2001-03-20 Thread Tatsuo Ishii
[Cced: to PostgreSQL hackers list] Alexander, I believe this problem was fixed in the latest JDBC driver, that is supposed to be shipped with 7.1. It asks your database which encoding is used for particular database while connecting to the database. So you should be able to see "select getdataba

[HACKERS] Re: Call for platforms

2001-03-20 Thread Thomas Lockhart
> SCO OpenServer 5 x86... OK, I see that Billy Allie recently updated FAQ_SCO to indicate demonstrated (?) support for OpenServer. I will reflect that in the platform support info. - Thomas ---(end of broadcast)--- TIP 5: Have

Re: [HACKERS] More on elog and error codes

2001-03-20 Thread Philip Warner
At 09:43 21/03/01 +1100, Philip Warner wrote: > >Code SQL Text >PGERR_TYPALREXI 02xxx "type %s cannot be created because it already exists" >PGERR_FUNCNOTYPE 02xxx "type %s used as argument %d of function %s doesn't >exist" > Peter, Just to clarify, because in a previous email you

[HACKERS] Re: Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Lamar Owen
On Tue, 20 Mar 2001, Thomas Lockhart wrote: > > I'll go ahead and upload the one I'm testing with right now if you'd like. > Not necessary, unless (I suppose) that you know the rpm for beta 4 is > broken. That vintage CVS tree behaved well enough for me try it out > afaicr... It's a good start

Re: [HACKERS] Call for platforms

2001-03-20 Thread Larry Rosenman
* Thomas Lockhart <[EMAIL PROTECTED]> [010320 20:04]: > OK, here is my current platform list taken from the -hackers list and > from Vince's web page. I'm sure I've missed at least a few reports, but > please confirm that platforms are actually running and passing > regression tests with recent be

[HACKERS] Call for platforms

2001-03-20 Thread Thomas Lockhart
OK, here is my current platform list taken from the -hackers list and from Vince's web page. I'm sure I've missed at least a few reports, but please confirm that platforms are actually running and passing regression tests with recent betas or the latest release candidate. If a platform you are ru

Re: [HACKERS] Re: Final Call: RC1 about to go out the door ...

2001-03-20 Thread Thomas Lockhart
> mklinux is older Motorola 68k-based systems > LinuxPPC is the newer powerPC-based systems Hmm. I have mklinux listed as being on the 750. My vague recollection is that the distinction is between NuBus and PCI machines (not necessarily in that order), but... I also vaguely recalled that the dis

[HACKERS] Re: Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Thomas Lockhart
> I'll go ahead and upload the one I'm testing with right now if you'd like. Not necessary, unless (I suppose) that you know the rpm for beta 4 is broken. That vintage CVS tree behaved well enough for me try it out afaicr... - Thomas ---(end of broadc

Re: [HACKERS] Re: Final Call: RC1 about to go out the door ...

2001-03-20 Thread Dominic J. Eidson
On Wed, 21 Mar 2001, Thomas Lockhart wrote: > > > >> Linux/PPC (LinuxPPC 2000 Q4 distro tested here; 2.2.18 kernel I think) > > > > What processor? Tatsuo had tested on a 603... > > > It's a Powerbook G3 (FireWire model), but I'm not sure which chip is > > > inside (and Apple's spec sheet i

[HACKERS] Re: Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Lamar Owen
On Tue, 20 Mar 2001, Thomas Lockhart wrote: > > Seeing that RC1 is in prep, is there a pressing need to upload and release beta > > 6 RPM's, or will it be a day or two before RC1? > Can I get the src rpm to give a try on Mandrake? I had trouble with > 7.0.3 (a mysterious disappearing file in the

Re: [HACKERS] pg_inherits: not found, but visible [IT GETS WORSE]

2001-03-20 Thread Joel Burton
On Tue, 20 Mar 2001, Ross J. Reedstrom wrote: > What kind of filesystem is the pgsql data tree living on? If you do a fsck, > does anything turn up in lost+found? > > Ross ext2, straight out of the box. It's in /var, which is a separate partition. fscking shows no errors, tells no lies, and no

[HACKERS] Re: Final Call: RC1 about to go out the door ...

2001-03-20 Thread Thomas Lockhart
> > >> Linux/PPC (LinuxPPC 2000 Q4 distro tested here; 2.2.18 kernel I think) > > > What processor? Tatsuo had tested on a 603... > > It's a Powerbook G3 (FireWire model), but I'm not sure which chip is > > inside (and Apple's spec sheet isn't too helpful)... > From what I can tell (which is

RE: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Mikheev, Vadim
> Further note: this bug does not arise in 7.0.* because in that code, > BufferSync will only pin buffers that have been dirtied in the current > transaction. This cannot affect a concurrent FlushRelationBuffers, > which should be holding exclusive lock on the table it's flushing. > > Or can it?

[HACKERS] Re: Final Call: RC1 about to go out the door ...

2001-03-20 Thread Thomas Lockhart
> >> Linux/PPC (LinuxPPC 2000 Q4 distro tested here; 2.2.18 kernel I think) > > > What processor? Tatsuo had tested on a 603... > It's a Powerbook G3 (FireWire model), but I'm not sure which chip is > inside (and Apple's spec sheet isn't too helpful)... >From what I can tell (which isn't m

Re: [HACKERS] pg_inherits: not found, but visible [IT GETS WORSE]

2001-03-20 Thread Ross J. Reedstrom
On Tue, Mar 20, 2001 at 08:03:16PM -0500, Joel Burton wrote: > > Yikes. It gets weirder. > > > I have > > Zope 2.3.1b2 (most recent version of Zope) > running on a Linux-Mandrake 7.2 box (server #1) > What kind of filesystem is the pgsql data tree living on? If you do a fsck, does anything t

[HACKERS] Re: Final Call: RC1 about to go out the door ...

2001-03-20 Thread Tom Lane
Thomas Lockhart <[EMAIL PROTECTED]> writes: >> HPUX 10.20 (HP-PA architecture) > Time to drop 9.2 from the list? I don't have it running here anymore. Is there anyone on the list who can test on HPUX 9? >> Linux/PPC (LinuxPPC 2000 Q4 distro tested here; 2.2.18 kernel I think) > Wha

[HACKERS] Re: Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Thomas Lockhart
> Seeing that RC1 is in prep, is there a pressing need to upload and release beta > 6 RPM's, or will it be a day or two before RC1? Can I get the src rpm to give a try on Mandrake? I had trouble with 7.0.3 (a mysterious disappearing file in the perl build) and would like to see where we are at wi

Re: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Tom Lane
>> I think the problem is that BufferSync unconditionally does PinBuffer >> on each buffer, and holds the pin during intervals where it's released >> BufMgrLock, even if there's not really anything for it to do on that >> buffer. If someone else is running FlushRelationBuffers then it's >> possib

Re: [HACKERS] pg_inherits: not found, but visible [IT GETS WORSE]

2001-03-20 Thread Joel Burton
Yikes. It gets weirder. Fixed the pg_inherits problem, went back to my Zoping, trying to optimize some views, and during another run, get an error that trelclasspq, one of my tables, couldn't open. Trying this out in psql, I get the same error message--the file doesn't exist. And, getting the o

[HACKERS] Re: Final Call: RC1 about to go out the door ...

2001-03-20 Thread Thomas Lockhart
> HPUX 10.20 (HP-PA architecture) Time to drop 9.2 from the list? > Linux/PPC (LinuxPPC 2000 Q4 distro tested here; 2.2.18 kernel I think) What processor? Tatsuo had tested on a 603... - Thomas ---(end of broadcast)---

RE: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Mikheev, Vadim
> I think the problem is that BufferSync unconditionally does PinBuffer > on each buffer, and holds the pin during intervals where it's released > BufMgrLock, even if there's not really anything for it to do on that > buffer. If someone else is running FlushRelationBuffers then it's > possible fo

Re: [HACKERS] pg_inherits: not found, but visible

2001-03-20 Thread Joel Burton
On Wed, 21 Mar 2001, Hiroshi Inoue wrote: > Joel Burton wrote: > > > > On Wed, 21 Mar 2001, Hiroshi Inoue wrote: > > > > > Joel Burton wrote: > > > > > > > > Postmaster crashed on me, and on restart, pg_inherits cannot be found. > > > > I can see it in pg_class (and it shows up w/ \dS), but any

Re: [HACKERS] pg_inherits: not found, but visible

2001-03-20 Thread Joel Burton
On Tue, 20 Mar 2001, Tom Lane wrote: > Joel Burton <[EMAIL PROTECTED]> writes: > >> and I could find a $PGDATA/base/18720/16567 file. > >> Could you find such a file ? > > > No. I do have the db directory, and all of the other file for the existing > > classes, but not this. > > Hm. You could

Re: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Tom Lane
Lamar Owen <[EMAIL PROTECTED]> writes: > Although I am now much more leery of our regression suite The regression tests are not at all designed to test concurrent behavior, and never have been. The parallel form runs some tests in parallel, true, but those tests are deliberately designed not to

Re: [HACKERS] pg_inherits: not found, but visible

2001-03-20 Thread Hiroshi Inoue
Joel Burton wrote: > > On Wed, 21 Mar 2001, Hiroshi Inoue wrote: > > > Joel Burton wrote: > > > > > > Postmaster crashed on me, and on restart, pg_inherits cannot be found. > > > I can see it in pg_class (and it shows up w/ \dS), but any attempt to > > > modify anything fails with "pg_inherits: N

Re: [HACKERS] pg_inherits: not found, but visible

2001-03-20 Thread Tom Lane
Joel Burton <[EMAIL PROTECTED]> writes: >> and I could find a $PGDATA/base/18720/16567 file. >> Could you find such a file ? > No. I do have the db directory, and all of the other file for the existing > classes, but not this. Hm. You could make an empty file by that name (just 'touch' it) and

Re: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Lamar Owen
On Tue, 20 Mar 2001, Tom Lane wrote: > This will not be RC1 :-( > 'Ive already gotten a > couple occurrences of Lamar's failure. Well, I was at least hoping it was a problem here -- particularly since I haven't been able to reproduce it. But, since it is not a local problem, I'm glad I caught it

Re: [HACKERS] Final Call: RC1 about to go out the door ...

2001-03-20 Thread Roberto Mello
On Tue, Mar 20, 2001 at 08:11:21PM +0100, Peter Eisentraut wrote: > > We need a supported platform list. Let's hear it. Linux 2.4.2 (Debian, Woody), glibc 2.2.2, gcc 2.95.3 (from CVS). -Roberto -- +| http://fslc.usu.edu USU Free Software & GNU/Linux Club|--+ Roberto

Re: [HACKERS] pg_inherits: not found, but visible

2001-03-20 Thread Joel Burton
On Wed, 21 Mar 2001, Hiroshi Inoue wrote: > Joel Burton wrote: > > > > Postmaster crashed on me, and on restart, pg_inherits cannot be found. > > I can see it in pg_class (and it shows up w/ \dS), but any attempt to > > modify anything fails with "pg_inherits: No such file or directory". > > >

Re: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Tom Lane
The Hermit Hacker <[EMAIL PROTECTED]> writes: > Okay, I roll'd an RC1 but haven't put it up for FTP yet ... I'll wait for > a few hours to see if anyone can reproduce this, and, if not, put out what > I've rolled ... This will not be RC1 :-( I'm been running one backend doing repeated iterations

Re: [HACKERS] pg_inherits: not found, but visible

2001-03-20 Thread Hiroshi Inoue
Joel Burton wrote: > > Postmaster crashed on me, and on restart, pg_inherits cannot be found. > I can see it in pg_class (and it shows up w/ \dS), but any attempt to > modify anything fails with "pg_inherits: No such file or directory". > > I've reindexed the database (w/postgres -P -O). Vacuumin

Re: [HACKERS] Final Call: RC1 about to go out the door ...

2001-03-20 Thread Vince Vielhaber
Go here to report or to see the list. http://www.postgresql.org/~vev/regress/ Vince. On Tue, 20 Mar 2001, Larry Rosenman wrote: > UnixWare 7, Rel 7.1.1, using UDK FS Compiler > FreeBSD 4.[23] > > LER > > >> Original Message << > > On 3/20/01, 1:11:21 PM, Pete

Re: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Tom Lane
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes: > Hmm, concurrent checkpoint? Probably we could simplify dirty test > in ByfferSync() - ie test bufHdr->cntxDirty without holding > shlock (and pin!) on buffer: should be good as long as we set > cntxDirty flag *before* XLogInsert in access methods. Hav

[HACKERS] pg_inherits: addt'l info

2001-03-20 Thread Joel Burton
I'm sorry, I should have included: PostgreSQL 7.1beta4 Linux-Mandrake 7.1 (very simiiar RedHat 7) Intel hardware -- Joel Burton <[EMAIL PROTECTED]> Director of Information Systems, Support Center of Washington ---(end of broadcast)--- TIP 3:

Re: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread The Hermit Hacker
On Tue, 20 Mar 2001, Tom Lane wrote: > Lamar Owen <[EMAIL PROTECTED]> writes: > > I'm hoping it was a problem on my machine -- educate me on > > what caused the error > > Well, that's exactly what I'd like to know. The direct cause of the > error is that DROP TABLE is finding that some other bac

Re: [HACKERS] Fw: [vorbis-dev] ogg123: shared memory by mmap()

2001-03-20 Thread Alfred Perlstein
* Bruce Momjian <[EMAIL PROTECTED]> [010320 14:10] wrote: > > > > The patch below adds: > > > > > > > > - acinclude.m4: A new macro A_FUNC_SMMAP to check that sharing > > > pages > > > > through mmap() works. This is taken from Joerg Schilling's star. > > > > - configure.in: A_FUNC_SMMAP > >

[HACKERS] pg_inherits: not found, but visible

2001-03-20 Thread Joel Burton
Postmaster crashed on me, and on restart, pg_inherits cannot be found. I can see it in pg_class (and it shows up w/ \dS), but any attempt to modify anything fails with "pg_inherits: No such file or directory". I've reindexed the database (w/postgres -P -O). Vacuuming fails (w/error above). What

[HACKERS] pgindent run?

2001-03-20 Thread Bruce Momjian
With RC1 nearing, when should I run pgindent? This is usually the time I do it. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.

Re: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Lamar Owen
On Tue, 20 Mar 2001, Tom Lane wrote: > Since no other backend should be trying to touch this temp table, > there's something pretty fishy here. I see. > Given that this is a parallel test, you may be looking at a > low-probability timing-dependent failure. I'd say set up the machine > and run

RE: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Mikheev, Vadim
> I'm rerunning to see if it is intermittent. Second run -- no > error. Running a third time..no error. Now I'm confused. > What would cause such an error, Tom? I'm going to check on my Hmm, concurrent checkpoint? Probably we could simplify dirty test in ByfferSync() - ie test bufHdr->cnt

Re: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Tom Lane
Lamar Owen <[EMAIL PROTECTED]> writes: > I'm hoping it was a problem on my machine -- educate me on > what caused the error Well, that's exactly what I'd like to know. The direct cause of the error is that DROP TABLE is finding that some other backend has a reference-count hold on a page of the

Re: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Lamar Owen
On Tue, 20 Mar 2001, Tom Lane wrote: > Lamar Owen <[EMAIL PROTECTED]> writes: > > DROP TABLE temptest; > > + NOTICE: FlushRelationBuffers(temptest, 0): block 0 is referenced (private 0, >global 1) > > + ERROR: heap_drop_with_catalog: FlushRelationBuffers returned -2 > > SELECT * FROM temptest;

Re: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Tom Lane
Lamar Owen <[EMAIL PROTECTED]> writes: > DROP TABLE temptest; > + NOTICE: FlushRelationBuffers(temptest, 0): block 0 is referenced (private 0, >global 1) > + ERROR: heap_drop_with_catalog: FlushRelationBuffers returned -2 > SELECT * FROM temptest; >> Hoo, that's interesting ... Exactly what

Re: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Lamar Owen
On Tue, 20 Mar 2001, Tom Lane wrote: > Lamar Owen <[EMAIL PROTECTED]> writes: > > DROP TABLE temptest; > > + NOTICE: FlushRelationBuffers(temptest, 0): block 0 is referenced (private 0, >global 1) > > + ERROR: heap_drop_with_catalog: FlushRelationBuffers returned -2 > > SELECT * FROM tempte

Re: [HACKERS] More on elog and error codes

2001-03-20 Thread Philip Warner
At 09:41 21/03/01 +1200, Christopher Sawtell wrote: >Just that it might be a good idea to incorporate the version / release >details in some way so that when somebody on the list is squeaking about >an error message it is obvious to the helper that the advice needed is to >upgrade from the Cre

Re: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread The Hermit Hacker
On Tue, 20 Mar 2001, Lamar Owen wrote: > Ok, thanks to our snowstorm :-0 I have been working on the beta 6 RPM situation > on my _slow_ notebook today (power outages for ten minutes at a time happening > at hour or so intervals due to 45mph+ winds and a foot of snow). > > Well, I have prelimi

Re: [HACKERS] More on elog and error codes

2001-03-20 Thread Philip Warner
At 17:35 20/03/01 +0100, Peter Eisentraut wrote: >Philip Warner writes: > >> elog(CACHELOOKUPFAIL, cacheItemThatFailed); > >The disadvantage of this approach, which I tried to explain in a previous >message, is that we might want to have different wordings for different >occurences of the same

[HACKERS] pg_dump - failed sanity check, type

2001-03-20 Thread Cedar Cox
(First of all, is this the right list?) When doing pg_dump testdb -u I get failed sanity check, type with oid 899762 was not found I searched my backend log for this oid and found something near the 'tryme' function. As far as I can find I have two functions defined with different args and

Re: [HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Tom Lane
Lamar Owen <[EMAIL PROTECTED]> writes: > DROP TABLE temptest; > + NOTICE: FlushRelationBuffers(temptest, 0): block 0 is referenced (private 0, >global 1) > + ERROR: heap_drop_with_catalog: FlushRelationBuffers returned -2 > SELECT * FROM temptest; Hoo, that's interesting ... Exactly what

Re: [HACKERS] Re: Patch application

2001-03-20 Thread Bruce Momjian
OK, seems there have been enough objections that I will not implement a "experts" page, nor change the way patches are applied. I will be posting a diff -c of any patches I have to munge into place, so people can see how stuff was merged into the code. It seems the problem of people having to m

Re: [HACKERS] Fw: [vorbis-dev] ogg123: shared memory by mmap()

2001-03-20 Thread Bruce Momjian
> > > The patch below adds: > > > > > > - acinclude.m4: A new macro A_FUNC_SMMAP to check that sharing > > pages > > > through mmap() works. This is taken from Joerg Schilling's star. > > > - configure.in: A_FUNC_SMMAP > > > - ogg123/buffer.c: If we have a working mmap(), use it to create >

Re: [HACKERS] /contrib 'cosmetic'

2001-03-20 Thread Bruce Momjian
Added to TODO: * Rename some /contrib modules from pg* to pg_* > On Mon, Mar 19, 2001 at 05:50:01PM +0100, Peter Eisentraut wrote: > > > > > > In future ... please ignore patches those ignore the /contrib's practice > > > -- the trouble is overhaul the contrib tree during each version

Re: [HACKERS] More on elog and error codes

2001-03-20 Thread Ross J. Reedstrom
On Wed, Mar 21, 2001 at 09:41:44AM +1200, Christopher Sawtell wrote: > On Tue, 20 Mar 2001 10:56, you wrote: > > Just that it might be a good idea to incorporate the version / release > details in some way so that when somebody on the list is squeaking about > an error message it is obvious to

[HACKERS] RE: Re: More on elog and error codes

2001-03-20 Thread Otto A. Hirr, Jr.
> So we need some good error numbering scheme. Any ideas? I'm a newbie, but have been following dev and have a few comments and these are thoughts not criticisms: 1) I've seen a huge mixture of "how to implement" to support some desired feature without first knowing "all" of the features tha

[SQL] Re: [HACKERS] triggered data change violation

2001-03-20 Thread Peter Eisentraut
Tom Lane writes: > Cedar Cox <[EMAIL PROTECTED]> writes: > > Added note: The trigger is a BEFORE trigger. > > AFAIK the "triggered data change" message comes out of the AFTER trigger > code. You sure you don't have any AFTER triggers on the table? Perhaps > ones added implicitly by a foreign-k

Re: [HACKERS] triggered data change violation

2001-03-20 Thread Tom Lane
Cedar Cox <[EMAIL PROTECTED]> writes: > Added note: The trigger is a BEFORE trigger. AFAIK the "triggered data change" message comes out of the AFTER trigger code. You sure you don't have any AFTER triggers on the table? Perhaps ones added implicitly by a foreign-key constraint?

Re: [HACKERS] Performance monitor signal handler

2001-03-20 Thread Bruce Momjian
I have talked to Jan over the phone, and he has convinced me that UDP is the proper way to communicate stats to the collector, rather than my shared memory idea. The advantages of his UDP approach is that the collector can sleep on the UDP socket rather than having the collector poll the shared m

Re: [HACKERS] Final Call: RC1 about to go out the door ...

2001-03-20 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > We need a supported platform list. Let's hear it. HPUX 10.20 (HP-PA architecture) Linux/PPC (LinuxPPC 2000 Q4 distro tested here; 2.2.18 kernel I think) regards, tom lane ---(end of broadc

Re: [HACKERS] triggered data change violation

2001-03-20 Thread Cedar Cox
On Tue, 20 Mar 2001, Tom Lane wrote: > Cedar Cox <[EMAIL PROTECTED]> writes: > > Added note: The trigger is a BEFORE trigger. > > AFAIK the "triggered data change" message comes out of the AFTER trigger > code. You sure you don't have any AFTER triggers on the table? Perhaps > ones added impl

Re: [HACKERS] More on elog and error codes

2001-03-20 Thread Christopher Sawtell
On Tue, 20 Mar 2001 10:56, you wrote: > I've looked at the elog calls in the source, about 1700 in total (only [ ... ] > So we need some good error numbering scheme. Any ideas? Just that it might be a good idea to incorporate the version / release details in some way so that when somebody on

[HACKERS] Beta 6 Regression results on Redat 7.0.

2001-03-20 Thread Lamar Owen
Ok, thanks to our snowstorm :-0 I have been working on the beta 6 RPM situation on my _slow_ notebook today (power outages for ten minutes at a time happening at hour or so intervals due to 45mph+ winds and a foot of snow). Well, I have preliminary RPM's built -- just need to work on the cont

RE: [HACKERS] Final Call: RC1 about to go out the door ...

2001-03-20 Thread Michael Ansley
Title: RE: [HACKERS] Final Call: RC1 about to go out the door ... Redhat Linux 7.0 (glibc 2.2-12, gcc 2.96-69) MikeA -Original Message- From: Peter Eisentraut To: The Hermit Hacker Cc: [EMAIL PROTECTED] Sent: 20/03/01 19:11 Subject: Re: [HACKERS] Final Call: RC1 about to go out the

Re: [HACKERS] triggered data change violation

2001-03-20 Thread Tom Lane
Cedar Cox <[EMAIL PROTECTED]> writes: >> AFAIK the "triggered data change" message comes out of the AFTER trigger >> code. You sure you don't have any AFTER triggers on the table? Perhaps >> ones added implicitly by a foreign-key constraint? > Not any that I wrote. Ok, the table def is: > CRE

Re: [SQL] Re: [HACKERS] triggered data change violation

2001-03-20 Thread Bruce Momjian
> A "triggered data change violation" happens everytime you change twice > within a transaction a value (column) that is part of a foreign key > constraint (don't recall exactly which part). > > This error shouldn't really happen, but I recall there were some > implementation and definition probl

Re: [HACKERS] Allowing WAL fsync to be done via O_SYNC

2001-03-20 Thread Bruce Momjian
Added to TODO: * Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options * Allow multiple blocks to be written to WAL with one write() > Bruce Momjian <[EMAIL PROTECTED]> writes: > > It is hard for me to imagine O_* being slower than fsync(), > > Not hard at all ---

[HACKERS] triggered data change violation

2001-03-20 Thread Cedar Cox
Added note: The trigger is a BEFORE trigger. -- Forwarded message -- To: [EMAIL PROTECTED] Date: Tue, 20 Mar 2001 20:43:59 +0200 (IST) Subject: triggered data change violation ERROR: triggered data change violation on relation "tblstsc2options" What is this? It doesn't happ

[HACKERS] Added to TODO

2001-03-20 Thread Bruce Momjian
Added to TODO: * Make elog(LOG) in WAL its own output type, distinct from DEBUG * Delay fsync() when other backends are about to commit too [fsync] * Determine optimal commit_delay value -- Bruce Momjian| http://candle.pha.pa.us [EMAI

Re: [HACKERS] Final Call: RC1 about to go out the door ...

2001-03-20 Thread Bruce Momjian
BSDI 4.01. [ Charset ISO-8859-1 unsupported, converting... ] > UnixWare 7, Rel 7.1.1, using UDK FS Compiler > FreeBSD 4.[23] > > LER > > >> Original Message << > > On 3/20/01, 1:11:21 PM, Peter Eisentraut <[EMAIL PROTECTED]> wrote regarding > Re: [HACKERS] Fina

Re: [HACKERS] Final Call: RC1 about to go out the door ...

2001-03-20 Thread Larry Rosenman
UnixWare 7, Rel 7.1.1, using UDK FS Compiler FreeBSD 4.[23] LER >> Original Message << On 3/20/01, 1:11:21 PM, Peter Eisentraut <[EMAIL PROTECTED]> wrote regarding Re: [HACKERS] Final Call: RC1 about to go out the door ...: > The Hermit Hacker writes: > >

Re: [HACKERS] FAQ: Current state of replication ?

2001-03-20 Thread Joe Conway
> 1. One "writer", many "reader" PostgreSQL servers. We will want to write > provisioning / configuration information centrally and can tolerate a > "writer" failuer for a time. > 2. Consitency at the transaction level. All changes to the "writer" server > will be wrapped in transactions, and ther

Re: [HACKERS] Final Call: RC1 about to go out the door ...

2001-03-20 Thread Peter Eisentraut
The Hermit Hacker writes: > We'd like to wrap up an RC1 and get this release happening this > year sometime :) Tom mentioned to me that he has no outstandings left on > his plate ... does anyone else have any *show stoppers* left that need to > be addressed, or can I package things up? I

RE: [HACKERS] Final Call: RC1 about to go out the door ...

2001-03-20 Thread Mikheev, Vadim
> And still no LAZY vacuum. *sigh* Patch will be available in a few days after release. Sorry, Alfred. Vadim ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl

RE: [HACKERS] Final Call: RC1 about to go out the door ...

2001-03-20 Thread Mikheev, Vadim
> We'd like to wrap up an RC1 and get this release happening > this year sometime :) Tom mentioned to me that he has no > outstandings left on his plate ... does anyone else have any > *show stoppers* left that need to be addressed, or can I package > things up? I wonder if anybody tried t

[GENERAL] Client can not connect to socket...

2001-03-20 Thread Chris Bowlby
I was configuring postmaster to allow more buffers to be used (1250 of them) and once that change was made, postmaster would no longer allow connections. I have since removed the option and it still does the same thing. I added -N 33 to it to see if she would recover to no avail... any ideas? C

Re: [HACKERS] Final Call: RC1 about to go out the door ...

2001-03-20 Thread Alfred Perlstein
* Tom Lane <[EMAIL PROTECTED]> [010320 10:21] wrote: > The Hermit Hacker <[EMAIL PROTECTED]> writes: > > Speak now, or forever hold your piece (where forever is the time > > between now and RC1 is packaged) ... > > I rather hope it's *NOT* And still no LAZY vacuum. *sigh* -- -Alfred

Re: [HACKERS] Final Call: RC1 about to go out the door ...

2001-03-20 Thread Tom Lane
The Hermit Hacker <[EMAIL PROTECTED]> writes: > Speak now, or forever hold your piece (where forever is the time > between now and RC1 is packaged) ... I rather hope it's *NOT* regards, tom lane ---(end of broadcast)

[HACKERS] Final Call: RC1 about to go out the door ...

2001-03-20 Thread The Hermit Hacker
Okay folks ... We'd like to wrap up an RC1 and get this release happening this year sometime :) Tom mentioned to me that he has no outstandings left on his plate ... does anyone else have any *show stoppers* left that need to be addressed, or can I package things up? Speak now,

Re: AW: [HACKERS] More on elog and error codes

2001-03-20 Thread Tom Lane
Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes: > PGELOG(ERROR, PGSQLSTATE_TYPE, ("type %s cannot be created because it already >exists", ...)) > put varargs into parentheses to avoid need for ... macros see Tom's proposal I'd be inclined to make it PGELOG((ERROR, PGSQLSTATE_TYPE, "type %s

Re: AW: [HACKERS] Re: More on elog and error codes

2001-03-20 Thread Larry Rosenman
Coming from an IBM Mainframe background, I'm used to ALL OS/Product messages having a message number, and a fat messages and codes book. I hope we can do that eventually. (maybe a database of the error numbers and codes?) LER >> Original Message << On 3/20/01

AW: [HACKERS] More on elog and error codes

2001-03-20 Thread Zeugswetter Andreas SB
> #define PGERR_TYPE 1854 #define PGSQLSTATE_TYPE "S0021"// char(5) SQLSTATE The standard calls this error variable SQLSTATE (look up in ESQL standard) first 2 chars are class next 3 are subclass "0" is e.g. Success "02000" is Data not found "U0xxx" user defined routine error xxx

[HACKERS] Re: src/test/regress/README duplicates SGML material

2001-03-20 Thread Peter Eisentraut
Thomas Lockhart writes: > Just make sure that we have a *complete* list of files which need to be > formatted from sgml to something other than HTML and postscript or pdf > and we'll get them built for the release. It's all documented: Developer's Guide -> Documentation -> Building the Document

Re: AW: [HACKERS] Re: More on elog and error codes

2001-03-20 Thread Peter Eisentraut
Zeugswetter Andreas SB writes: > > SQL9x specifies some error codes, with no particular numbering scheme > > other than negative numbers indicate a problem afaicr. > > > > Shouldn't we map to those where possible? > > Yes, it defines at least a few dozen char(5) error codes. These are hierarchica

[HACKERS] Re: [DOCS] Re: src/test/regress/README duplicates SGML material

2001-03-20 Thread Bruce Momjian
> It's all documented: Developer's Guide -> Documentation -> Building the > Documentation -> Plain Text Files. > > The three affected text files are: > INSTALL > HISTORY > src/test/regress/README > > The INSTALL file hasn't been updated in a while, but I am keeping my eye > on it, but we need t

  1   2   >