[SQL] 8K Limit, and Replication
Hello, I have heard of this infamous 8k limit. I have a couple of questions. 1. Does this mean that if I have a large object that I am inserting into a table, like an image it has to be 8k or less? 2. When will this be fixed? 3. Does anyone know the status of the replication capabilities in PGSQL? J On Wed, 6 Sep 2000, Craig May wrote: >Hi, > >I have a tables having this structure: > >ID (int) | _ID (int) | Name (String) > > >_ID is the parent of ID. > >I'm looking for the best method to perform a cascade delete. For example, I >delete _ID, it in turn deletes ID, and should ID also be an entry within _ID, it >would continue through the chain. > >For example: > >0 0 Base >1 0 Sib1 >2 0 Sib2 >3 0 Sib3 >4 1 Sib1_1 >5 1 Sib1_2 > > >Deleting Base would remove all the entries. Deleting Sib1 would delete Sib1_1 >and Sib1_2. >Can anyone help out here? > >Regards, >Craig May > >Enth Dimension >http://www.enthdimension.com.au > -- -- CommandPrompt - http://www.commandprompt.com OpenDocs, LLC. - http://www.opendocs.org LinuxPorts - http://www.linuxports.com LDP - http://www.linuxdoc.org -- Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. --
Re: [SQL] Using a postgres table to maintain unique id?
>However, I also use Postgres (7.0.2) throughout this >application and it seems cleaner to me to keep the current >id value in a table and just use postgres to provide access >(with a trigger function to increment the id on access). Why not a sequence? >Is this reasonable? Is it fast? (I need 10 or more IDs >generated each second.) Can I avoid having the table >gradually fill with "old" rows for this entry, and this >avoid the need to run VACUUM ANALYZE periodically? The only problem I have had with this type of thing is when a number gets deleted, it does not get recycled. Joshua Drake > >Any tips on how to implement the trigger would be >appreciated. (Is it possible to generate an int8 sequence >value?) > >Thanks! >-- >Steve Wampler- SOLIS Project, National Solar Observatory >[EMAIL PROTECTED] > -- -- CommandPrompt - http://www.commandprompt.com OpenDocs, LLC. - http://www.opendocs.org LinuxPorts - http://www.linuxports.com LDP - http://www.linuxdoc.org -- Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. --
Re: [SQL] PostgreSQL HOWTO
Hello, I do not see how it puts the Postgres community in a bad light, although I do see how the author is a moron. J On Thu, 18 Jan 2001, Kaare Rasmussen wrote: >Whoever wrote this is putting the PostgreSQL community in a bad light: > >http://www.linux.org/docs/ldp/howto/PostgreSQL-HOWTO-4.html > >Maybe someone can change the document, or make the author change it? > > -- -- CommandPrompt - http://www.commandprompt.com OpenDocs, LLC. - http://www.opendocs.org LinuxPorts - http://www.linuxports.com LDP - http://www.linuxdoc.org -- Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. --
[SQL] PostgreSQL HOWTO & LDp
Hello, I am the Webmaster of the LDP... What should I know? Joshua Drake On Thu, 18 Jan 2001, Tom Lane wrote: >Kaare Rasmussen <[EMAIL PROTECTED]> writes: >> Whoever wrote this is putting the PostgreSQL community in a bad light: >> http://www.linux.org/docs/ldp/howto/PostgreSQL-HOWTO-4.html >> Maybe someone can change the document, or make the author change it? > >(Rolls eyes...) See the archives for past discussion of this. We have >been unable to persuade the LDP that the maintainer of the Postgres >HOWTO is unfit to be trusted with sharp objects, let alone a HOWTO. >If we could take it away from him, we'd gladly do so. > > regards, tom lane > -- -- CommandPrompt - http://www.commandprompt.com OpenDocs, LLC. - http://www.opendocs.org LinuxPorts - http://www.linuxports.com LDP - http://www.linuxdoc.org -- Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. --
Re: [SQL] PostgreSQL HOWTO
>|> Best web-scripting (and compiling) language is PHP+Zend compiler >|> PHP is extremely powerful as it combines the power of Perl, >|> Java, C++, Javascript into one single language and it runs on >|> all OSes - unixes and Windows NT/95. > >it seems that the author never used any other think then PHP ... I am afraid I would disagree. I have used all of the languages he metions and for the Web, PHP is the best. > > >Ciao > Alvar > > -- -- CommandPrompt - http://www.commandprompt.com OpenDocs, LLC. - http://www.opendocs.org LinuxPorts - http://www.linuxports.com LDP - http://www.linuxdoc.org -- Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. --
Re: [SQL] PostgreSQL HOWTO
Hello, I have temporarily removed the PostgreSQL HOWTO, pending peer review. Joshua Drake On Thu, 18 Jan 2001, Brett W. McCoy wrote: >On Thu, 18 Jan 2001, Poet/Joshua Drake wrote: > >> >it seems that the author never used any other think then PHP ... >> >> I am afraid I would disagree. I have used all of the languages he metions >> and for the Web, PHP is the best. > >I think it all depends on what you are building. PHP is good for small >projects, but I would go with something more scalable for large systems, >like EJB/servlets or Mason -- something that has more content management & >templating features. > >-- Brett > http://www.chapelperilous.net/~bmccoy/ >--- >Did you know the University of Iowa closed down after someone stole the book? > -- -- CommandPrompt - http://www.commandprompt.com OpenDocs, LLC. - http://www.opendocs.org LinuxPorts - http://www.linuxports.com LDP - http://www.linuxdoc.org -- Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. --
[SQL] Postgres-HOWTO
Has been removed from the LDP website. J -- -- CommandPrompt - http://www.commandprompt.com OpenDocs, LLC. - http://www.opendocs.org LinuxPorts - http://www.linuxports.com LDP - http://www.linuxdoc.org -- Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. --
Re: [SQL] Postgres-HOWTO
Hello, The Postgres team from PGSQL, Inc. has agreed to provide us with a new version. J On Wed, 7 Feb 2001, Christopher Sawtell wrote: >On Tue, 06 Feb 2001 08:50, Poet/Joshua Drake wrote: >> Has been removed from the LDP website. > >Good news indeed! > >Now what are we going to do with it? > >Can the original document's source be made available so that >somebody can do the needed work without having to re-key. > >There is a _lot_ of very good information in there buried underneath the >... um ... > > > -- -- CommandPrompt - http://www.commandprompt.com OpenDocs, LLC. - http://www.opendocs.org LinuxPorts - http://www.linuxports.com LDP - http://www.linuxdoc.org -- Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. --
Re: [SQL] outer joins
Hello, I believe these are supported in 7.1 On Wed, 4 Apr 2001, [iso-8859-4] Algirdas ©akmanas wrote: >Hi all, > >I'm new to postgre, I've changed my work and consequently now i'm moving >from MS plaform. >In MS SQL there are such constructs left or right outer join, in postgres >there are no such thing > >Can You offer me strategy to make query that selects from table (a) and >joins to it another (b) >on e.g. a.id=b.aid but joins so that in case there is no value in table b >NULL is left in result: >in MS SQL i've used query: > >select a.id, b.name from a left outer join b on a.id=b.aid > >table a table b > >id | aid | name >--- >11 | Tom >23 | Sam > >result: >a.id | b.name >- >1 | Tom >2 | NULL > >thank you in advance > >Algirdas ©akmanas >IT manager >+370 99 90369 >[EMAIL PROTECTED] >Grafton Entertainment >http://www.tvnet.lt > > > >---(end of broadcast)--- >TIP 2: you can get off all lists at once with the unregister command >(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED]) > -- -- CommandPrompt - http://www.commandprompt.com OpenDocs, LLC. - http://www.opendocs.org LinuxPorts - http://www.linuxports.com LDP - http://www.linuxdoc.org -- Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. -- ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [SQL] Same question about PostgreSql
>How stable is PostgreSql ? >I know, PostgreSql doesn't support 'prepare ' operation, is it successful to >use one for OLTP databases ? Speaking from experience, I have personally stress tested Postgres under loads of over 512 persistent connections with our LXP application server with zero problems. J > > >Thanks for responds. > >Good luck. > >Sergey. > > > > > > > >---(end of broadcast)--- >TIP 6: Have you searched our list archives? > >http://www.postgresql.org/search.mpl > -- -- CommandPrompt - http://www.commandprompt.com OpenDocs, LLC. - http://www.opendocs.org LinuxPorts - http://www.linuxports.com LDP - http://www.linuxdoc.org -- Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. -- ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
[SQL] [OT] Book on Postgres (Not a question)
Hello, I know this is off topic but I thought you might like to know that the following book explains how to compile, install and secure postgresql. It can be purchased from http://www.linuxports.com/ (just click on the books) and 20% goes back to the OpenSource Documentation Fund. THe Original Announcement: This email is to announce the new OpenDocs Publication: Securing and Optimizing Linux: RedHat Edition Including with the book are the Linux Central CD's of: RedHat 6.2 RedHat 6.2 Powertools The retail price for the book is 49.95 but if you preorder it no the price is only 39.95!. And of course since it is an OpenDocs Publication a percentage of the Gross Profits go to the Open Source Documentation Fund. Below is an abbreviated Table of Contents: Linux Installation Descriptions of programs packages we must uninstall for securities reasons Descriptions of programs that must be uninstalled after installation of the server Linux General Security Linux General Optimization Linux Kernel Linux TCP/IP Network Management Linux IPCHAINS Linux Masquerading and Forwarding Linux Compiler functionality Linux sXid Linux Logcheck Linux PortSentry Linux OpenSSH Client/Server Linux SSH2 Client/Server Linux Tripwire 2.2.1 Linux Tripwire ASR 1.3.1 Linux GnuPG Set Quota on your Linux system Linux DNS and BIND Server Linux Sendmail Server (includes 8.10.1) Linux IMAP & POP Server Enable IMAP or POP via the tcp-wrappers inetd super server Linux OPENSSL Server Linux FreeS/WAN VPN Linux OpenLDAP Server Linux PostgreSQL Database Server Linux Squid Proxy Server Linux MM - Shared Memory Library for Apache Linux Apache Web Server Linux Webalizer Linux FAQ-O-Matic Linux Webmail IMP Linux Samba Server Linux FTP Server Linux Backup and Restore Tweaks, Tips and Administration tasks Obtaining Requests for Comments (RFCs) Thanks! [EMAIL PROTECTED] -- -- CommandPrompt - http://www.commandprompt.com OpenDocs, LLC. - http://www.opendocs.org LinuxPorts - http://www.linuxports.com LDP - http://www.linuxdoc.org -- Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. --
