[HACKERS] Call for platforms (Solaris)
Hi I've been running RC3 regression tests, starting with a FreeBSD 4.2-STABLE and a Solaris 7 Sparc box. Both tests ran without any problems. I tried Solaris 8 Sparc next: it still suffered from the same unix socket problems. I had a look at the code and it seems to me that the use of unix sockets in RC3 is still enabled, even though it (appearently) doesn't work reliably on Solaris. Since it was rather strange that RC3 did work correctly on Solaris 7 but not 8, I also ran regression tests on another Solaris 7 and another 8 box, with the same results. Since I still didn't trust it, I also ran RC1 again on both Solaris 7 and 8; same result. And now things start getting weird. A little more than a week ago the RC1 regression tests ran with on average 10-15 tests randomly failing. Now, however, I can run the regression several times without any test failing. But if I run the regression test enough times (4-6 times), I do have tests that fail (about 2-5). The configuration of these servers hasn't changed in the last months and I used the same RC1 source and binaries. Can somebody confirm whether pgsql Solaris does or does not work correctly out-of-the-box? Disabling unix sockets will probably fix all these problems, so I'm naturally wondering whether unix socket will or will not be disabled in pgsql 7.1... Regards, Mathijs Ps. Vince, could you remove test results 46 and 47? I don't trust them anymore. -- "A book is a fragile creature. It suffers the wear of time, it fears rodents, the elements, clumsy hands." Umberto Eco ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Call for platforms (HP-UX)
Giles Lean <[EMAIL PROTECTED]> writes: > I'm not sure how interesting these differences are anymore -- is there > anyone familiar enough with floating point to determine if the results > are acceptable (although currently unexpected :-) or not? Differences in the last couple of decimal places in the geometry test are definitely not a cause for worry. Although we've tried to create exact-match reference files for the most popular platforms, I think that's largely an exercise in time-wasting. Eventually we will figure out a way to make the geometry output round off a few digits, and then the cross-platform differences should mostly vanish. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Call for platforms (HP-UX)
> Okay, here are my results: > > Box 1: C180 (2.0 PA8000), HPUX 10.20 > > Compile with gcc: all tests pass > Compile with cc: two lines of diffs in geometry (attached) > > Box 2: 715/75 (1.1 PA7100LC), HPUX 10.20 > > Compile with gcc: all tests pass > Compile with cc: all tests pass I haven't had time to look at this further yet, except to build 7.1RC3 a couple of times with the HP ANSI C compiler today: PA-RISC 1.1 code (-Ae +O2 +DAportable): all tests pass PA-RISC 2.0 code (-Ae +O2 +DA2.0 +DS2.0): geometry failures I'm not sure how interesting these differences are anymore -- is there anyone familiar enough with floating point to determine if the results are acceptable (although currently unexpected :-) or not? Regards, Giles ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] Re: Call for platforms
> Thanks! I'm not too worried about 1.4.2, but be sure to let us know what > the problem was; it may help out someone else... NetBSD-1.4.2/i386 passes all tests with 7.1RC3. My previous test failure on this platform was due to the timezone information on the test system not being standard; once that was corrected all tests pass. It is still necessary to add -ltermcap after -ledit in src/Makefile.global to have functional history editing in psql. Regards, Giles ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[HACKERS] pgmonitor completed
[ BCC to admin] I have completed my PostgreSQL session monitor utility, pgmonitor. I have recently added the ability to start/stop the postmaster. I considered adding the ability to set postmaster/postgres command flags, but decided they are not changed frequently enough. It still does not work on Solaris under 7.1RC because no Solaris users have gotten ps_status working on that platform. I plan to write PostgreSQL articles for the next few weeks. -- 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.| Drexel Hill, Pennsylvania 19026 P G M O N I T O R pgmonitor, version 0.42 The main web site for pgmonitor is: http://greatbridge.org/project/pgmonitor/projdisplay.php You can download the most recent version from ftp://ftp.greatbridge.org/pub/pgmonitor This tool allows monitoring of PostgreSQL activity. It requires Tcl/Tk 8.0 or later. It may require modification of the 'ps' flags for certain platforms. It is known to run on *BSD, Linux, and HPUX. Pgmonitor only works when run on the database server machine. To use it remotely, log into the remote machine, set the DISPLAY variable to point to your local X server, and start pgmonitor. Pgmonitor will then run on the remote machine, but will display on your local machine. Pgmonitor uses 'ps' to display backend process activity. It uses 'gdb' to display running queries, and 'kill' to cancel queries and terminate database connections. Pgmonitor stores your most recent refresh and sort settings in the file ~/.pgmonitor. This file is used to reload your defaults every time pgmonitor is started. If you are running PostgreSQL 7.1.0 or earlier, the 'query' button will not work unless you compile PostgreSQL with debug symbols (-g), or apply the supplied patch 'query_display.diff' and recompile PostgreSQL. The later method is recommended. For porting assistance, there are 'set debug' and 'set show_all' options in the script. 'debug' outputs status information while pgmonitor running, and 'show_all' shows all PostgreSQL user processes, such as the postmaster. Bruce Momjian <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Re: RC3 ...
> > Can you use ps2pdf to generate PDF? It is a utility that comes with > > ghostscript. I know versions >= 6.0 are fine. > > PDF files generated from postscript with Adobe Acrobat are usually of > much higher quality than those generated by ghostscript. It seems that > ghostscript encodes rendered (bitmaps) documents, while Acrobat generates > PDF files of a quality similar to the original postscript documents. > > You would definately have much hihger quality PDF files if someone with > access to Acrobat would step forward. Too bad Acrobat is soo expensive :( This is only true of ghostscript version <6.0. Pre-6.0 could only encode non-bitmapped fonts if they were the standard Adobe 35. 6.0 and later do full curve rendering for all fonts, at least they should. My book PDF's that were used to print certainly were not bitmapped fonts. I have tons of PDF's on my web site, and none use bitmapped fonts. All used ghoscript 6.01. -- 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.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Re: RC3 ... and rpms...
I have no idea if what I say is true about the PG distribution by PG people, but I have noticed than in the rpms of other distros the postgresql-devel rpms do not include all the .h files necessary to build PG extensions. For instance the rtree.h and itup.h and gist.h headers are missing. Could you please ensure that all the headers are taken into account when you write your spec file. May be also in the tar.gz or tar.bz2 distribution (bz2 is more effective than gz and available on all platforms) you add a developer file that list all the required headers, so that package builders know which files to include. It seems that the rpm distributions will go as: postgresql postgresql-docs (user and manager docs) postgresql-devel (header files and developper docs) Cheers. [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Re: RC3 ...
On Fri, Apr 06, 2001 at 09:23:35PM -0400, Bruce Momjian allegedly wrote: > > > Thomas, will you be doing .pdf files? I have had requests to put that > > > in the Debian documentation package. > > > > afaik, I don't have the means to generate pdf directly. Pointers would > > be appreciated, if there are mechanisms available on Linux boxes. > > > > We have had lots of offers of help for these conversions, so when the > > hardcopy is ready we can ask someone to convert from there. OK? > > Can you use ps2pdf to generate PDF? It is a utility that comes with > ghostscript. I know versions >= 6.0 are fine. PDF files generated from postscript with Adobe Acrobat are usually of much higher quality than those generated by ghostscript. It seems that ghostscript encodes rendered (bitmaps) documents, while Acrobat generates PDF files of a quality similar to the original postscript documents. You would definately have much hihger quality PDF files if someone with access to Acrobat would step forward. Too bad Acrobat is soo expensive :( Regards, Mathijs -- It's not that perl programmers are idiots, it's that the language rewards idiotic behavior in a way that no other language or tool has ever done. Erik Naggum ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Re: RC3 ...
On Fri, 6 Apr 2001, Bruce Momjian wrote: > > > That strikes me as an awfully web-centric view of things. Not everyone > > > has an always-on high-speed Internet link. > > > > > > If you want to make the docs and TODO.detail be a separate chunk of the > > > split distribution, that's fine with me. But I don't agree with > > > removing them from the full tarball. > > > > > > OTOH, if Marc was only thinking of removing the pre-built docs from the > > > tarball, I don't object to that. I'm not sure why those weren't > > > distributed as separate tarballs from the get-go. I just say that the > > > doc sources are part of the source distribution... > > > > But, why? That sounds like a highly DSL-centric view of things *grin* If > > someone really wants docs, what hurts a second GET ftp call? > > A major issue is that we don't regenerate docs for 7.1.1 or later, so > the 7.1 docs carry for all the 7.1.X releases. That would seem to argue > for a separate tarball for docs so people don't redownload the docs > again for 7.1.1. Okay, unless someone can come up with a really good argument *for* why docs has to be included as part of the main tar file, I'm going to change the distributin generating script so that it generates a .src.tar.gz file seperate from the .doc.tar.gz file, which will make .src.tar.gz ~6Meg instead of the 8meg we are currently forcing ppl to download ... Peter E, is there anything part of the configure/make procedure that *requires* pgsql/doc to be there else it will break? If so, can you possibly put it as a test "if docs exists, deal with it, else ignore"? ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] Re: RC3 ...
> > That strikes me as an awfully web-centric view of things. Not everyone > > has an always-on high-speed Internet link. > > > > If you want to make the docs and TODO.detail be a separate chunk of the > > split distribution, that's fine with me. But I don't agree with > > removing them from the full tarball. > > > > OTOH, if Marc was only thinking of removing the pre-built docs from the > > tarball, I don't object to that. I'm not sure why those weren't > > distributed as separate tarballs from the get-go. I just say that the > > doc sources are part of the source distribution... > > But, why? That sounds like a highly DSL-centric view of things *grin* If > someone really wants docs, what hurts a second GET ftp call? A major issue is that we don't regenerate docs for 7.1.1 or later, so the 7.1 docs carry for all the 7.1.X releases. That would seem to argue for a separate tarball for docs so people don't redownload the docs again for 7.1.1. -- 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.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Re: RC3 ...
> > Thomas, will you be doing .pdf files? I have had requests to put that > > in the Debian documentation package. > > afaik, I don't have the means to generate pdf directly. Pointers would > be appreciated, if there are mechanisms available on Linux boxes. > > We have had lots of offers of help for these conversions, so when the > hardcopy is ready we can ask someone to convert from there. OK? Can you use ps2pdf to generate PDF? It is a utility that comes with ghostscript. I know versions >= 6.0 are fine. -- 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.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Re: RC3 ...
> Thomas, will you be doing .pdf files? I have had requests to put that > in the Debian documentation package. afaik, I don't have the means to generate pdf directly. Pointers would be appreciated, if there are mechanisms available on Linux boxes. We have had lots of offers of help for these conversions, so when the hardcopy is ready we can ask someone to convert from there. OK? - Thomas ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[HACKERS] Re: RC3 ...
> > OTOH, if Marc was only thinking of removing the pre-built docs from the > > tarball, I don't object to that. I'm not sure why those weren't > > distributed as separate tarballs from the get-go. I just say that the > > doc sources are part of the source distribution... >From the get-go, the docs were not, uh, useful docs. They have grown quite a bit from 1996 (with sources and formatting, probably by orders of magnitude). - Thomas ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] Re: RC3 ...
On Fri, 6 Apr 2001, Tom Lane wrote: > >> At 2Meg, is there a reason why we include any of the docs as part of the > >> standard tar ball? It shouldn't be required to compile, so should be able > >> to be left out of the main tar ball and downloaded seperately as required > >> .. thereby shrinking the distribution to <6Meg from its current 8 ... > > > Can we drop TODO.detail from the tarball too? No need to include that, > > I think. The web site has nice links to it now. Uncompressed it is > > 1.314 megs. > > That strikes me as an awfully web-centric view of things. Not everyone > has an always-on high-speed Internet link. > > If you want to make the docs and TODO.detail be a separate chunk of the > split distribution, that's fine with me. But I don't agree with > removing them from the full tarball. > > OTOH, if Marc was only thinking of removing the pre-built docs from the > tarball, I don't object to that. I'm not sure why those weren't > distributed as separate tarballs from the get-go. I just say that the > doc sources are part of the source distribution... But, why? That sounds like a highly DSL-centric view of things *grin* If someone really wants docs, what hurts a second GET ftp call? ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Re: RC3 ...
>> At 2Meg, is there a reason why we include any of the docs as part of the >> standard tar ball? It shouldn't be required to compile, so should be able >> to be left out of the main tar ball and downloaded seperately as required >> .. thereby shrinking the distribution to <6Meg from its current 8 ... > Can we drop TODO.detail from the tarball too? No need to include that, > I think. The web site has nice links to it now. Uncompressed it is > 1.314 megs. That strikes me as an awfully web-centric view of things. Not everyone has an always-on high-speed Internet link. If you want to make the docs and TODO.detail be a separate chunk of the split distribution, that's fine with me. But I don't agree with removing them from the full tarball. OTOH, if Marc was only thinking of removing the pre-built docs from the tarball, I don't object to that. I'm not sure why those weren't distributed as separate tarballs from the get-go. I just say that the doc sources are part of the source distribution... regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Re: RC3 ...
> > Can we drop TODO.detail from the tarball too? No need to include that, > > I think. The web site has nice links to it now. Uncompressed it is > > 1.314 megs. > > That strikes me as an awfully web-centric view of things. Not everyone > has an always-on high-speed Internet link. > > If you want to make the docs and TODO.detail be a separate chunk of the > split distribution, that's fine with me. But I don't agree with > removing them from the full tarball. But isn't TODO.detail mostly of interest to people who use CVS? I see your point, though. -- 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.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
Re: [HACKERS] Re: RC3 ...
On Fri, 6 Apr 2001, Bruce Momjian wrote: > > On Fri, 6 Apr 2001, Thomas Lockhart wrote: > > > > > > > The docs are ready for shipment. > > > > Even better ... > > > > Okay, let's let this sit as RC3 for the next week... > > > > > > I'll go ahead and start generating hardcopy, though I understand that it > > > is no longer allowed into the shipping tarball :( > > > > At 2Meg, is there a reason why we include any of the docs as part of the > > standard tar ball? It shouldn't be required to compile, so should be able > > to be left out of the main tar ball and downloaded seperately as required > > .. thereby shrinking the distribution to <6Meg from its current 8 ... > > Can we drop TODO.detail from the tarball too? No need to include that, > I think. The web site has nice links to it now. Uncompressed it is > 1.314 megs. Definitely, I think TODO.detail should be refer'd to by the TODO file, but not included in the distribution itself ... ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Re: RC3 ...
Thomas Lockhart wrote: >> > The docs are ready for shipment. >> Even better ... >> Okay, let's let this sit as RC3 for the next week... > >I'll go ahead and start generating hardcopy, though I understand that it >is no longer allowed into the shipping tarball :( > >Lamar, do you plan to continue to package the hardcopy somewhere in the >RPMs? If so, I'll have them ready soon. Thomas, will you be doing .pdf files? I have had requests to put that in the Debian documentation package. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47 GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C "A gentle answer turns away wrath, but a harsh word stirs up anger."Proverbs 15:1 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Re: RC3 ...
> On Fri, 6 Apr 2001, Thomas Lockhart wrote: > > > > > The docs are ready for shipment. > > > Even better ... > > > Okay, let's let this sit as RC3 for the next week... > > > > I'll go ahead and start generating hardcopy, though I understand that it > > is no longer allowed into the shipping tarball :( > > At 2Meg, is there a reason why we include any of the docs as part of the > standard tar ball? It shouldn't be required to compile, so should be able > to be left out of the main tar ball and downloaded seperately as required > .. thereby shrinking the distribution to <6Meg from its current 8 ... Can we drop TODO.detail from the tarball too? No need to include that, I think. The web site has nice links to it now. Uncompressed it is 1.314 megs. -- 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.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] Re: RC3 ...
On Fri, 6 Apr 2001, The Hermit Hacker wrote: > On Fri, 6 Apr 2001, Thomas Lockhart wrote: > > > > > The docs are ready for shipment. > > > Even better ... > > > Okay, let's let this sit as RC3 for the next week... > > > > I'll go ahead and start generating hardcopy, though I understand that it > > is no longer allowed into the shipping tarball :( > > At 2Meg, is there a reason why we include any of the docs as part of the > standard tar ball? It shouldn't be required to compile, so should be able > to be left out of the main tar ball and downloaded seperately as required > .. thereby shrinking the distribution to <6Meg from its current 8 ... We may already do so, but include the upgrade instructions, first time install instructions and basic startup. Then bundle the docs as they normally come in the tarball as a separate set (alone). A number of other packages are done this way. If we want to include a be-all-end-all we can do that too. Of course other doc formats/sets will also be available. Vince. -- == Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net 56K Nationwide Dialup from $16.00/mo at Pop4 Networking Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] Re: RC3 ...
On Fri, 6 Apr 2001, Thomas Lockhart wrote: > > > The docs are ready for shipment. > > Even better ... > > Okay, let's let this sit as RC3 for the next week... > > I'll go ahead and start generating hardcopy, though I understand that it > is no longer allowed into the shipping tarball :( At 2Meg, is there a reason why we include any of the docs as part of the standard tar ball? It shouldn't be required to compile, so should be able to be left out of the main tar ball and downloaded seperately as required .. thereby shrinking the distribution to <6Meg from its current 8 ... ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Re: RC3 ...
Thomas Lockhart wrote: > I'll go ahead and start generating hardcopy, though I understand that it > is no longer allowed into the shipping tarball :( > Lamar, do you plan to continue to package the hardcopy somewhere in the > RPMs? If so, I'll have them ready soon. I didn't for 7.0, IIRC. Or maybe I did for 7.0, but then didn't for 7.0.2? I'll have to go back to the changelog I am open to suggestion -- should it be part of the main postgresql RPM with the source and html docs, or should it be a separate package, such as postgresql-hardcopy-docs? Ideas? Comments? The 'Internals' document is still in the main package, FWIW. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] RC3 ...
> On Fri, 6 Apr 2001, The Hermit Hacker wrote: > > > > > For those that want to get in before the rush, I'm going to do an announce > > this evenin to -general and -announce ... > > > > Vince, can you make appropriate changes to the WebSite as far as linking > > to it is concerned, so that the mirrors pick up the new links also? > > Does it look like this it gonna be the one? It's stable and all that? > Once it's on the website no matter what moniker it's got (up to and > including "DANGER THIS IS BROKEN SO DON'T USE IT") it will be viewed > as the golden apple so I want to avoid another full mailbox. I'll > probably wait till tomorrow evening (if you announce tonite) just to > be sure. Smart man, that Vince. :-) -- 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.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[HACKERS] Re: RC3 ...
> > The docs are ready for shipment. > Even better ... > Okay, let's let this sit as RC3 for the next week... I'll go ahead and start generating hardcopy, though I understand that it is no longer allowed into the shipping tarball :( Lamar, do you plan to continue to package the hardcopy somewhere in the RPMs? If so, I'll have them ready soon. - Thomas ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Re: Call for platforms
> If somethings happen this weekend, I *MAY* have a HP9000/433s (M68K) > running NetBSD to play with That would be great. I *know* that there are some m68k machines around somewhere on this planet, and it would be a shame to not have NetBSD tested for the release... - Thomas ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
Re: [HACKERS] Duplicate databases...
On Fri, 6 Apr 2001, Tom Lane wrote: > On closer look, I'll bet that "brandon" and "postgres" have the > same usesysid assigned in pg_shadow. Need to change one of them. That was it - both were 501. Thanks. -- Dominic J. Eidson "Baruk Khazad! Khazad ai-menu!" - Gimli --- http://www.the-infinite.org/ http://www.the-infinite.org/~dominic/ ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] Duplicate databases...
Vacuuming pg_database should make the bogus entries go away ... regards, tom lane ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Duplicate databases...
"Dominic J. Eidson" <[EMAIL PROTECTED]> writes: >> postgres | brandon <-- Incorrect >> postgres | postgres >> smc_is_neteng | dominic >> template1 | brandon <-- Incorrect >> template1 | postgres >> wwwrun| brandon <-- Incorrect >> wwwrun| postgres >> (17 rows) Actually, I take that back, this isn't a connection-time issue... On closer look, I'll bet that "brandon" and "postgres" have the same usesysid assigned in pg_shadow. Need to change one of them. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] RC3 ...
On Fri, 6 Apr 2001, The Hermit Hacker wrote: > On Fri, 6 Apr 2001, Vince Vielhaber wrote: > > > On Fri, 6 Apr 2001, The Hermit Hacker wrote: > > > > > On Fri, 6 Apr 2001, Peter Eisentraut wrote: > > > > > > > The Hermit Hacker writes: > > > > > > > > > baring any major blow ups, the only thing we are waiting on is docs ... > > > > > > > > The docs are ready for shipment. > > > > > > Even better ... > > > > > > Okay, let's let this sit as RC3 for the next week, as soon as someone > > > makes a change, I'll do up a new RC# that night ... if we can get a nice > > > quiet period where nobody pops up with "just one more thing", let's try > > > for a release for next Friday ... *cross fingers* *grin* > > > > So does RC3 have the docs and the odbc thing mentioned earlier rolled > > in? > > Yes, just re-bundled it ... Cool! Vince. -- == Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net 56K Nationwide Dialup from $16.00/mo at Pop4 Networking Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
Re: [HACKERS] More Problems
Matthew <[EMAIL PROTECTED]> writes: > -- dumping out user-defined functions > failed sanity check, type with oid 101993741 was not found Looks like you have a function that refers to a since-deleted type. You'll need to find and drop the function (which may mean manually deleting its pg_proc row, since there's no way to name the function to DROP FUNCTION if one of its parameters is a now-unknown type). Another possibility is that the type still exists but you deleted its owning user from pg_shadow; that will confuse pg_dump too. In that case you can just create a new user with the same usesysid, or you can update the type's typowner field in pg_type to refer to some existing user. Try "select * from pg_type where oid = 101993741" to figure out which situation applies ... regards, tom lane ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Duplicate databases...
I just love to reply to myself.. On Fri, 6 Apr 2001, Dominic J. Eidson wrote: [Snip] > postgres | brandon <-- Incorrect > postgres | postgres > smc_is_neteng | dominic > template1 | brandon <-- Incorrect > template1 | postgres > wwwrun| brandon <-- Incorrect > wwwrun| postgres > (17 rows) > > > Any idea what would cause this" > > (The "<-- Incorrect" was added by me.. ) dominic=# select version(); version - PostgreSQL 7.0.2 on i686-pc-linux-gnu, compiled by gcc egcs-2.91.66 (1 row) -- Dominic J. Eidson "Baruk Khazad! Khazad ai-menu!" - Gimli --- http://www.the-infinite.org/ http://www.the-infinite.org/~dominic/ ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Re: TODO list
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes: > Something to remember: currently we update t_infomask (set > HEAP_XMAX_COMMITTED etc) while holding share lock on buffer - > we have to change this before block CRC implementation. Yeah, we'd lose some concurrency there. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] Duplicate databases...
dominic=# \l List of databases Database| Owner ---+-- aleal | aleal arivera | arivera bbeyer| bbeyer brandon | brandon brandon | postgres dominic | dominic ds3 | agould keystone | dominic kperoni | kperoni mgrooms | mgrooms postgres | brandon<-- Incorrect postgres | postgres smc_is_neteng | dominic template1 | brandon<-- Incorrect template1 | postgres wwwrun| brandon<-- Incorrect wwwrun| postgres (17 rows) Any idea what would cause this" (The "<-- Incorrect" was added by me.. ) -- Dominic J. Eidson "Baruk Khazad! Khazad ai-menu!" - Gimli --- http://www.the-infinite.org/ http://www.the-infinite.org/~dominic/ ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] RC3 ...
On Fri, 6 Apr 2001, Vince Vielhaber wrote: > On Fri, 6 Apr 2001, The Hermit Hacker wrote: > > > On Fri, 6 Apr 2001, Peter Eisentraut wrote: > > > > > The Hermit Hacker writes: > > > > > > > baring any major blow ups, the only thing we are waiting on is docs ... > > > > > > The docs are ready for shipment. > > > > Even better ... > > > > Okay, let's let this sit as RC3 for the next week, as soon as someone > > makes a change, I'll do up a new RC# that night ... if we can get a nice > > quiet period where nobody pops up with "just one more thing", let's try > > for a release for next Friday ... *cross fingers* *grin* > > So does RC3 have the docs and the odbc thing mentioned earlier rolled > in? Yes, just re-bundled it ... ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
Re: [HACKERS] RC3 ...
On Fri, 6 Apr 2001, The Hermit Hacker wrote: > On Fri, 6 Apr 2001, Peter Eisentraut wrote: > > > The Hermit Hacker writes: > > > > > baring any major blow ups, the only thing we are waiting on is docs ... > > > > The docs are ready for shipment. > > Even better ... > > Okay, let's let this sit as RC3 for the next week, as soon as someone > makes a change, I'll do up a new RC# that night ... if we can get a nice > quiet period where nobody pops up with "just one more thing", let's try > for a release for next Friday ... *cross fingers* *grin* So does RC3 have the docs and the odbc thing mentioned earlier rolled in? Vince. -- == Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net 56K Nationwide Dialup from $16.00/mo at Pop4 Networking Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] RC3 ...
On Fri, 6 Apr 2001, Peter Eisentraut wrote: > The Hermit Hacker writes: > > > baring any major blow ups, the only thing we are waiting on is docs ... > > The docs are ready for shipment. Even better ... Okay, let's let this sit as RC3 for the next week, as soon as someone makes a change, I'll do up a new RC# that night ... if we can get a nice quiet period where nobody pops up with "just one more thing", let's try for a release for next Friday ... *cross fingers* *grin* ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] RC3 ...
The Hermit Hacker writes: > baring any major blow ups, the only thing we are waiting on is docs ... The docs are ready for shipment. -- Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/ ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
RE: [HACKERS] Re: TODO list
> To be perfectly clear: I have actually seen bug reports trace to > problems that I think a block-level CRC might have detected (not > corrected, of course, but at least the user might have realized he had > flaky hardware a little sooner). So I do not say that the upside to > a block CRC is nil. But I am unconvinced that it exceeds the > downside, in development effort, runtime, false failure reports > (is that CRC error really due to hardware trouble, or a software bug > that failed to update the CRC? and how do you get around the CRC error > to get at your data??) etc etc. Something to remember: currently we update t_infomask (set HEAP_XMAX_COMMITTED etc) while holding share lock on buffer - we have to change this before block CRC implementation. Vadim ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] RC3 ...
On Fri, 6 Apr 2001, Vince Vielhaber wrote: > On Fri, 6 Apr 2001, The Hermit Hacker wrote: > > > > > For those that want to get in before the rush, I'm going to do an announce > > this evenin to -general and -announce ... > > > > Vince, can you make appropriate changes to the WebSite as far as linking > > to it is concerned, so that the mirrors pick up the new links also? > > Does it look like this it gonna be the one? It's stable and all that? > Once it's on the website no matter what moniker it's got (up to and > including "DANGER THIS IS BROKEN SO DON'T USE IT") it will be viewed > as the golden apple so I want to avoid another full mailbox. I'll > probably wait till tomorrow evening (if you announce tonite) just to > be sure. baring any major blow ups, the only thing we are waiting on is docs ... ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
Re: [HACKERS] RC3 ...
On Fri, 6 Apr 2001, The Hermit Hacker wrote: > > For those that want to get in before the rush, I'm going to do an announce > this evenin to -general and -announce ... > > Vince, can you make appropriate changes to the WebSite as far as linking > to it is concerned, so that the mirrors pick up the new links also? Does it look like this it gonna be the one? It's stable and all that? Once it's on the website no matter what moniker it's got (up to and including "DANGER THIS IS BROKEN SO DON'T USE IT") it will be viewed as the golden apple so I want to avoid another full mailbox. I'll probably wait till tomorrow evening (if you announce tonite) just to be sure. Vince. -- == Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net 56K Nationwide Dialup from $16.00/mo at Pop4 Networking Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
RE: [HACKERS] Re: RC3 ... anyone have anything left outstanding?
> FWIW, I confirm that horology-no-DST-before-1970 is good; it passes on > HPUX. Can anyone confirm horology-solaris-1947? How to test it? All default tests are Ok on my Solaris. Vadim ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] RC3 ...
Tom Lane wrote: > > It looks like you wrapped the intermediate (broken) state of > interfaces/odbc/convert.c that Hiroshi had in there for a few hours. > Dunno if this is important enough to re-wrap RC3 for; it might affect > a few ODBC users ... Just as I was getting ready to upload a quickie RC3 RPMset... :-) -- Lamar Owen WGCR Internet Radio 1 Peter 4:11 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Re: RC3 ... anyone have anything left outstanding?
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes: >> FWIW, I confirm that horology-no-DST-before-1970 is good; it passes on >> HPUX. Can anyone confirm horology-solaris-1947? > How to test it? All default tests are Ok on my Solaris. If the horology test shows as passing, then we're set. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
Re: [HACKERS] RC3 ...
It looks like you wrapped the intermediate (broken) state of interfaces/odbc/convert.c that Hiroshi had in there for a few hours. Dunno if this is important enough to re-wrap RC3 for; it might affect a few ODBC users ... regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] More Problems
My nightly dump of one of my databases started failing Wednesday night and I'm not sure what is going on. When I pg_dump this one database (others on this machine are fine) I get this output from pg_dump -- last builtin oid is 17216 -- reading user-defined types -- reading user-defined functions -- reading user-defined aggregates -- reading user-defined operators -- reading user-defined tables -- finding Triggers for relation: 'jobs' [snip] ... -- finding DEFAULT expression for attr: 'id' -- finding the attrs and types for table: 'testassignments' -- finding DEFAULT expression for attr: 'id' -- finding DEFAULT expression for attr: 'standby' -- finding the attrs and types for table: 'pagedata' -- finding DEFAULT expression for attr: 'id' -- flagging inherited attributes in subtables -- dumping out database comment -- dumping out user-defined types -- dumping out tables -- dumping out user-defined procedural languages -- dumping out user-defined functions failed sanity check, type with oid 101993741 was not found relevant info: pg7.0.2 on redhat 6.1, 700MHz Athlon, 256M, linux software mirror hard drives. btw: This is a completely different server at a different location from the one that was having problems two weeks ago and thank you all for the help then, I don't think I emailed a thank you, it was a busy day. ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Foreign Key & Rule confusion WAS: Lost Trigger(s)?
Ack... All my current history keeping methods are done via triggers on tables (generally set off by various RI_ triggers). Not real good if it didn't set off those triggers for me. I'm sure rules are a ditto in that case for others. I was hoping for a way to prevent the RI trigger from failing if there wasn't anything to do anyway -- SELECT FOR DELETE -- if no results ignore, if there were results delete the results. Delete does a search anyway, this would lock the rows and later get rid of them. A hack, and I have no idea how it would pan out -- but that's would produce what I expected to happen. Otherwise I change all the ON DELETE DO INSTEAD NOTHING rules to triggers which see if the parent still exists (and doesn't allow deletion if it does) otherwise it cancels the delete. Not a nice solution. -- Rod Taylor There are always four sides to every story: your side, their side, the truth, and what really happened. - Original Message - From: "Tom Lane" <[EMAIL PROTECTED]> To: "Rod Taylor" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, April 06, 2001 11:20 AM Subject: Re: [HACKERS] Foreign Key & Rule confusion WAS: Lost Trigger(s)? > "Rod Taylor" <[EMAIL PROTECTED]> writes: > > I must apologize, I was copying from one screen to another due to > > network outage and gave a bad example -- missed the most important > > part. > > > There should have been an AS ON DELETE TO junk DO INSTEAD NOTHING; > > rule. > > Ah so. With that in place, I see what you are talking about: > > regression=# DELETE FROM junk_parent WHERE col = 1; > ERROR: SPI_execp() failed in RI_FKey_cascade_del() > regression=# DELETE FROM junk_parent WHERE col = 2; > ERROR: SPI_execp() failed in RI_FKey_cascade_del() > > > > The RI_FKey_cascade_del() trigger fails on the second delete attempt. > > To me it should ignore the error if there wasn't anything to delete in > > the first place. > > Well, I think the issue is something different. Right now, referential > integrity triggers are implemented as issuing actual queries --- which > are subject to rule rewrites. It strikes me that perhaps this is wrong, > and a referential integrity operation should proceed without regard to > rules. > > If you think that rules indeed should be able to affect referential > integrity updates, then it would probably be better that neither of > these examples fail (ie, the RI triggers should not complain about their > queries having been rewritten to nothing). > > I don't see a good argument for raising an error on the first delete and > not the second. Either ref integrity is subject to rules, or it's not. > > Next question: should a trigger be able to defeat an RI update? That > can happen now, too. > > regards, tom lane > ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] INSERT Issues
On Thu, Apr 05, 2001 at 07:16:49PM -0400, Rod Taylor wrote:
> CREATE TABLE junk (
> col SERIAL PRIMARY KEY
> );
>
> INSERT INTO junk (col) DEFAULT VALUES;
>
> INSERT INTO junk DEFAULT VALUES:
>
>
> Second insert works, first one fails.
>
> INSERT INTO table [ ( column [, ...] ) ]
> { DEFAULT VALUES | VALUES ( expression [, ...] ) | SELECT query }
>
>
> The column list should just be ignored correct?
>
Hmm, the BNF from SQL1992 actually is:
::=
INSERT INTO
::=
[]
| DEFAULT VALUES
::=
So the grammar is right to reject your first example.
According to the rules for :
2) An that specifies DEFAULT VALUES is
equivalent to an that specifies a
of the form
VALUES (DEFAULT, . . . )
where the number of "DEFAULT" entries is equal to the number of
columns of T.
So the proper spelling of your first version is:
INSERT INTO junk (col) VALUES (DEFAULT);
Does that work for you?
Ross
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Re: [HACKERS] Foreign Key & Rule confusion WAS: Lost Trigger(s)?
"Rod Taylor" <[EMAIL PROTECTED]> writes: > I must apologize, I was copying from one screen to another due to > network outage and gave a bad example -- missed the most important > part. > There should have been an AS ON DELETE TO junk DO INSTEAD NOTHING; > rule. Ah so. With that in place, I see what you are talking about: regression=# DELETE FROM junk_parent WHERE col = 1; ERROR: SPI_execp() failed in RI_FKey_cascade_del() regression=# DELETE FROM junk_parent WHERE col = 2; ERROR: SPI_execp() failed in RI_FKey_cascade_del() > The RI_FKey_cascade_del() trigger fails on the second delete attempt. > To me it should ignore the error if there wasn't anything to delete in > the first place. Well, I think the issue is something different. Right now, referential integrity triggers are implemented as issuing actual queries --- which are subject to rule rewrites. It strikes me that perhaps this is wrong, and a referential integrity operation should proceed without regard to rules. If you think that rules indeed should be able to affect referential integrity updates, then it would probably be better that neither of these examples fail (ie, the RI triggers should not complain about their queries having been rewritten to nothing). I don't see a good argument for raising an error on the first delete and not the second. Either ref integrity is subject to rules, or it's not. Next question: should a trigger be able to defeat an RI update? That can happen now, too. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] INSERT Issues
create table junk (col SERIAL); INSERT INTO junk (col) VALUES (DEFAULT); ERROR: parser: parse error at or near "DEFAULT"; > INSERT INTO junk (col) VALUES (DEFAULT); > > Does that work for you? > > Ross > ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[HACKERS] RC3 ...
For those that want to get in before the rush, I'm going to do an announce
this evenin to -general and -announce ...
Vince, can you make appropriate changes to the WebSite as far as linking
to it is concerned, so that the mirrors pick up the new links also?
Thanks ..
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Re: Integer to float function
Thomas Lockhart <[EMAIL PROTECTED]> writes: > Try using int2()/int4()/int8() instead of integer(). >> Why is that NOT documented under "Matematical functions"? > Because we haven't received any patches to document it? ;) Or because it's not a mathematical function. I don't think that datatype conversion functions belong under that heading. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] INSERT Issues
"Rod Taylor" <[EMAIL PROTECTED]> writes:
> INSERT INTO table [ ( column [, ...] ) ]
> { DEFAULT VALUES | VALUES ( expression [, ...] ) | SELECT query }
The documentation is wrong here, not the code. SQL92 defines the syntax
as
::=
INSERT INTO
::=
[]
| DEFAULT VALUES
::=
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Foreign Key & Rule confusion WAS: Lost Trigger(s)?
"Rod Taylor" <[EMAIL PROTECTED]> writes: > Not quite as expected. I didn't expect deleting the 2 from the > primary table to fail because the CASCADE DELETE wasn't able to run on > the second (even though no values existed in that table). But it *doesn't* fail. At least not in the versions I tried. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
[HACKERS] Re: Integer to float function
> > > integer (float_expression) or int (float_expression) DO work on > > RedHat6.2/PostgreSQL6.5 and DO NOT work on Mandrake/PostgreSQL7.0.2 > > Try using int2()/int4()/int8() instead of integer(). > Why is that NOT documented under "Matematical functions"? Because we haven't received any patches to document it? ;) - Thomas ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Foreign Key & Rule confusion WAS: Lost Trigger(s)?
Not quite as expected. I didn't expect deleting the 2 from the primary table to fail because the CASCADE DELETE wasn't able to run on the second (even though no values existed in that table). I suppose it does run properly (blocks all delete attempts) -- but I just didn't expect it to error out on values which didn't exist in the second table -- thereby blocking the deletion from the primary or referred table.. Tried against 7.1beta3 and 7.1beta5. -- Rod Taylor There are always four sides to every story: your side, their side, the truth, and what really happened. - Original Message - From: "Tom Lane" <[EMAIL PROTECTED]> To: "Rod Taylor" <[EMAIL PROTECTED]> Cc: "Hackers List" <[EMAIL PROTECTED]> Sent: Friday, April 06, 2001 1:54 AM Subject: Re: [HACKERS] Foreign Key & Rule confusion WAS: Lost Trigger(s)? > "Rod Taylor" <[EMAIL PROTECTED]> writes: > > Found the issue. Try out the attached SQL in a fresh database. > > And? AFAICT it behaves as expected, in either 7.0.2 or current ... > > regards, tom lane > ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[HACKERS] INSERT Issues
CREATE TABLE junk (
col SERIAL PRIMARY KEY
);
INSERT INTO junk (col) DEFAULT VALUES;
INSERT INTO junk DEFAULT VALUES:
Second insert works, first one fails.
INSERT INTO table [ ( column [, ...] ) ]
{ DEFAULT VALUES | VALUES ( expression [, ...] ) | SELECT query }
The column list should just be ignored correct?
--
Rod Taylor
There are always four sides to every story: your side, their side, the
truth, and what really happened.
BEGIN:VCARD
VERSION:2.1
N:Taylor;Rod;B
FN:Taylor, Rod B
ORG:BarChord Entertainment Inc.;System Operation and Development
TITLE:Chief Technical Officer
ADR;WORK:;;;Toronto;Ontario;;Canada
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Toronto, Ontario=0D=0ACanada
X-WAB-GENDER:2
URL:
URL:http://www.barchord.com
BDAY:19790401
EMAIL;INTERNET:[EMAIL PROTECTED]
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
EMAIL;INTERNET:[EMAIL PROTECTED]
REV:20010405T231649Z
END:VCARD
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Re: TODO list
> If we're in the business of expending cycles to guard against > nil-probability risks, let's checksum our executables every time we > start up, to make sure they're not overwritten. Actually, we'd better > re-checksum program text memory every few seconds, in case RAM dropped > a bit since we looked last. And let's follow every memcpy by a memcmp > to make sure that didn't drop a bit. Heck, let's keep a CRC on every Why does it sound like you have problems with radiation eating away at your live memory for satellite operations? ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[HACKERS] Foreign Key & Rule confusion RE: Lost Trigger(s)?
Found the issue. Try out the included SQL.
I had honestly expected the second delete to work properly as nothing
had to be removed that table.
The rule was added as a temporary measure to protect the data
currently in the table -- without the intent of otherwise impeding the
other information's use. I suppose I forgot that the table wouldn't be
looked at as the rule is checked quite early.
CREATE TABLE junk_parent (
col SERIAL PRIMARY KEY
);
INSERT INTO junk_parent DEFAULT VALUES;
INSERT INTO junk_parent DEFAULT VALUES;
INSERT INTO junk_parent DEFAULT VALUES;
CREATE TABLE junk (
col int4 NOT NULL REFERENCES junk_parent(col) ON UPDATE CASCADE ON
DELETE CASCADE
);
INSERT INTO junk VALUES ('1');
DELETE FROM junk_parent WHERE col = 1;
DELETE FROM junk_parent WHERE col = 2;
--
Rod Taylor
There are always four sides to every story: your side, their side, the
truth, and what really happened.
BEGIN:VCARD
VERSION:2.1
N:Taylor;Rod;B
FN:Taylor, Rod B
ORG:BarChord Entertainment Inc.;System Operation and Development
TITLE:Chief Technical Officer
ADR;WORK:;;;Toronto;Ontario;;Canada
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Toronto, Ontario=0D=0ACanada
X-WAB-GENDER:2
URL:
URL:http://www.barchord.com
BDAY:19790401
EMAIL;INTERNET:[EMAIL PROTECTED]
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
EMAIL;INTERNET:[EMAIL PROTECTED]
REV:20010405T232956Z
END:VCARD
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[HACKERS] Integer to float function
Einar Karttunen wrote: > > > > > integer (float_expression) or int (float_expression) DO work on > RedHat6.2/PostgreSQL6.5 and DO NOT work on Mandrake/PostgreSQL7.0.2 > Try using int2()/int4()/int8() instead of integer(). The intn() functions > convert the float to a integer n bytes long, in normal cases you probably > want to use int4(). > Einar, Much obliged. int4() has done a job. Why is that NOT documented under "Matematical functions"? Regards, Steven. -- *** Steven Vajdic (BSc/Hon, MSc) Senior Software Engineer Motorola Australia Software Centre (MASC) 2 Second Avenue, Technology Park Adelaide, South Australia 5095 email: [EMAIL PROTECTED] email: [EMAIL PROTECTED] Ph.: +61-8-8168-3435 Fax:+61-8-8168-3501 Front Office (Ph): +61-8-8168-3500 mobile: +61 (0)419 860 903 AFTER WORK email: [EMAIL PROTECTED] *** ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
