Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
On Sun, Jun 27, 2004 at 11:11:32AM -0700, Ron St-Pierre wrote:
STATEMENT: ALTER TABLE victoria.eodData DROP COLUMN tickDate;
ERROR: tables can have at most 1600 columns
STATEMENT: ALTER TABLE victoria.eodData ADD COLUMN tickerID
On Mon, 2004-06-28 at 14:37, Jaime Casanova wrote:
> Hi all,
>
> There is a way to actually eliminate those dropped tables so they
> don't affect the 1600 columns limit? I know it's very difficult to end
> up with this problem but apparently "it is" posible.
>
You may want to try recreating the
Hi all,
There is a way to actually eliminate those dropped tables so they don't affect the 1600 columns limit? I know it's very difficult to end up with this problem but apparently "it is" posible.
Thanx in advance,
Jaime Casanova
Tom Lane <[EMAIL PROTECTED]> wrote:
Alvaro Herrera <[EMAIL P
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Sun, Jun 27, 2004 at 11:11:32AM -0700, Ron St-Pierre wrote:
>> STATEMENT: ALTER TABLE victoria.eodData DROP COLUMN tickDate;
>> ERROR: tables can have at most 1600 columns
>> STATEMENT: ALTER TABLE victoria.eodData ADD COLUMN tickerID INTEGER;
>> E
On Sun, Jun 27, 2004 at 11:11:32AM -0700, Ron St-Pierre wrote:
> I found this error in /var/log/messages yesterday after a cron job
> wouldn't complete:
> STATEMENT: ALTER TABLE victoria.eodData DROP COLUMN tickDate;
> ERROR: tables can have at most 1600 columns
> STATEMENT: ALTER TABLE v
I found this error in /var/log/messages yesterday after a cron job
wouldn't complete:
STATEMENT: ALTER TABLE victoria.eodData DROP COLUMN tickDate;
ERROR: tables can have at most 1600 columns
STATEMENT: ALTER TABLE victoria.eodData ADD COLUMN tickerID INTEGER;
ERROR: tables can have at
