Anoop Bhat <ABhat at trustwave.com> writes:
> I previously had replication working from a master to a backup. I recently moved it from that backup to another in a different location.
>
> I noticed that neither of my backups had this one particular column from a particular table which stored user information.
>
> This column happened to be the password column (sort of important)
>
> The column definition is
>
>  password            | character varying(256)   |
>
>
> Is there any reason that this column would be blank on both backup
> servers. Am I missing something?

No reason I can think of; the only reason I'd see for this would be if
you had altered the table schemas by hand to introduce the password
column, so that somehow the data escaped being captured in the first
place.

Thus, the way I could see it happening is if you added password column
to all tables *WITHOUT* using "EXECUTE SCRIPT".

In that case, then (in some versions of Slony-I), the new password
column would not have been captured in the log trigger function
information, and, as a consequence, the password, not being captured
would not be replicated to other nodes.

That explanation shouldn't be valid for the 1.2 branch.  It *may* not
be true for 1.1; not 100% certain...
-- 
select 'cbbrowne' || '@' || 'cbbrowne.com';
http://www3.sympatico.ca/cbbrowne/oses.html
Actually, typing random  strings in the Finder does  the equivalent of
filename  completion.    (Discussion  in  comp.os.linux.misc   on  the
intuitiveness of commands: file completion vs. the Mac Finder.)