Mon Nov 1 08:25:57 PDT 2010
- Previous message: [Slony1-general] Slony1-general Digest, Vol 44, Issue 16
- Next message: [Slony1-general] attack of the timezone
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In addition to my previous posts: I suggest (for slony 1.2.2x): ALTER TABLE sl_archive_count ALTER COLUMN ac_timestamp TYPE timestamp with time zone; ALTER TABLE sl_confirm ALTER COLUMN con_timestamp TYPE timestamp with time zone; ALTER TABLE sl_registry ALTER COLUMN reg_timestamp TYPE timestamp with time zone; ALTER TABLE sl_event ALTER COLUMN ev_timestamp TYPE timestamp with time zone; Probably slony 2.0.x needs the same changes. Regards, Ger On 11/01/2010 04:15 PM, Christopher Browne wrote: > Ger Timmens <Ger.Timmens at adyen.com> writes: >> Can we change the definitions of all 'timestamp' columns >> from 'timestamp without time zone' to timestamp with time stamp' >> in slony (we are using 1.2.20 rightnow). > > Sure, you could submit DDL requests via the slonik command EXECUTE > SCRIPT > <http://slony.info/documentation/1.2/stmtddlscript.html> > > The script would consist of a series of ALTER TABLE commands, one for > each column to be thus altered. > > I suspect you'll find this to be a mighty expensive operation, as it: > > a) locks all the tables (in 1.2, ALL replicated tables, in 2.0, just > the ones that need to be altered) for the duration, and > > b) fairly likely leads to the affected tables being rewritten, so all > the old tuples are dead, so they need vacuuming rather badly. > > So, expensive, but it can certainly be done.
- Previous message: [Slony1-general] Slony1-general Digest, Vol 44, Issue 16
- Next message: [Slony1-general] attack of the timezone
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list