Re: [HACKERS] Lazy constraints / defaults

keeps all information in pg_class, pg_attribute everyone can get how the changes ware made. -- Regards, Michał Zaborowski (TeXXaS) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] Lazy constraints / defaults

, then DEFAULT, then UPDATE on all rows in chunks, then NOT NULL... Can it be little simpler? -- Regards, Michał Zaborowski (TeXXaS) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] constraint with no check

in troubles. Also explicit lock release can help with bulk updates. You see - maybe it is not a problem - but doing all that some how silly job - day by day... is boring. Hope it can help. -- Regards, Michał Zaborowski (TeXXaS) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [HACKERS] Sorting Improvements for 8.4

works nice. -- Regards, Michał Zaborowski (TeXXaS) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

Re: [HACKERS] VLDB Features

be much faster that single-thread load - surprisingly - at least for me. -- Regards, Michał Zaborowski (TeXXaS) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your