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
>

-- 
--
<COMPANY>CommandPrompt    - http://www.commandprompt.com    </COMPANY>
<PROJECT>OpenDocs, LLC.    - http://www.opendocs.org    </PROJECT>
<PROJECT>LinuxPorts     - http://www.linuxports.com     </PROJECT>
<WEBMASTER>LDP        - http://www.linuxdoc.org    </WEBMASTER>
--
Instead of asking why a piece of software is using "1970s technology," 
start asking why software is ignoring 30 years of accumulated wisdom. 
--