++This message is intended for
+adult webamsters. See removal info at the bottom of this page.
++
Dear Webmaster,
Do you ever wonder why Paysite Webmasters Pay $20-$30 per signup? Start earn
> "dej" == Jackson, DeJuan <[EMAIL PROTECTED]> writes:
>> if you insert a new row, isn't the sequence automatically
>> inserted?
>>
dej> It is if you use table defaults. (see 'create table', and
dej> 'netval()')
Thanks for the tip; Richard Lynch <[EMAIL PROTECTED]> had
Matt Vanderpol wrote:
> There is a maximum of about 8k for each record in the table.
> There is a maximum of 4k for each varchar that you have.
> There is a maximum of 1k that can be passed in any one field on a select
> query.
> The first two points are documented and make sense. The combinatio
> We use Prostgres 6.3.2 for our production system, but the Postgres
> tables is growing when the data updated (time travel?). Could any one
> help me to stop this time travel problem, since it make our system slow,
> and data corrputed frequently, our table size is about 150 MB (after
> vacuum),
At 14:34 +0300 on 12/7/98, Andy wrote:
> We use Prostgres 6.3.2 for our production system, but the Postgres
> tables is growing when the data updated (time travel?). Could any one
> help me to stop this time travel problem, since it make our system slow,
> and data corrputed frequently, our tabl
Deal All,
In the Postgres 6.3 tutorial there is information that the time travel
is not longer supported as follows:
>>As of Postgres v6.2, time travel is no longer supported. There are several reasons
>for this:
>>performance impact, storage size, and a pg_time file which grows toward infini
