http://www.slony.info/bugzilla/show_bug.cgi?id=217

Christopher Browne <cbbrowne at ca.afilias.info> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|slony1-bugs at lists.slony.inf |ssinger at ca.afilias.info
                   |o                           |
             Status|NEW                         |ASSIGNED

--- Comment #12 from Christopher Browne <cbbrowne at ca.afilias.info> 2011-06-09 09:38:42 PDT ---
It scares me that decoding trigger arguments required an SPI function.

Actually, poking at pg_trigger suggests that the problem isn't at the Slony
level...  I wonder who came up with the notion that the following was
reasonable...

slonyregress1 at localhost->  select tgnargs, tgargs from pg_trigger where tgnargs
> 0;
 tgnargs |                           tgargs
---------+------------------------------------------------------------
       3 | \x5f736c6f6e795f72656772657373310031006b00
       1 | \x5f736c6f6e795f726567726573733100
       3 | \x5f736c6f6e795f72656772657373310032006b00
       1 | \x5f736c6f6e795f726567726573733100
       3 | \x5f736c6f6e795f72656772657373310034006b00
       1 | \x5f736c6f6e795f726567726573733100
       3 | \x5f736c6f6e795f72656772657373310035006b76766b767676766b00
       1 | \x5f736c6f6e795f726567726573733100
(8 rows)

I'd be inclined to feed some griping about this representation up to
pgsql-hackers, in the hopes of getting something nicer, maybe?

Not that that's too likely for 9.1 :-)

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.