]
> Kevin Kempter writes:
> > we have a few not null constraints we want to drop on very large tables.
> > Unfortunately the drop's are taking hours. Is there a way to drop a not
> > null constraint via the system catalogs?
>
> Dropping a NOT NULL constraint is a trivial operation. The problem is
Kevin Kempter writes:
> we have a few not null constraints we want to drop on very large tables.
> Unfortunately the drop's are taking hours. Is there a way to drop a not null
> constraint via the system catalogs?
Dropping a NOT NULL constraint is a trivial operation. The problem is
probably t
Hi All;
we have a few not null constraints we want to drop on very large tables.
Unfortunately the drop's are taking hours. Is there a way to drop a not null
constraint via the system catalogs?
Thanks in advance
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes
Ireneusz Pluta writes:
> - when playing with pg_filedump I noticed that last pages of the table
> are always initially reported as damaged, as they come, then, as newer
> pages get allocated and filled, these initially bad pages "become
> valid", as in the following example repeating the same p
Hello,
I have a server, 8.4.3, where I get intermittent and rather rare cases
of "invalid page headers". Quick search over the pg lists shows a
general advice to "check your hardware". Yes, I need to schedule a
downtime and perform some checks.
However, let me also share with you what I noti
Hi,
I can't to put the pgAgent service using parameter postgres to (Windows
username) and (database username) without to use the password parameter
inside the connection string (hostaddr=127.0.0.1 dbname=postgres
user=postgres password=ourPassword).
If I put Windows user and postgres to database
I recently shrunk over 90% of two huge tables on our production database
by partitioning 3-month recent data into 3 separate partitions each and
got rid of the rest of the data. Despite the smaller sizes, our queries
now run slower. The following complex query/view with 8 joined tables,
especiall
>> time echo '\timing \\select * from table1 where id = 123;' | psql
>> In the above query. the 'timing' will time the database time and
>> the 'time' command at the very start will time the complete time
>> for the query including network time.
>
> No, the 'timing' will say how long it took to se
