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

           Summary: TRUNCATE support broken in master(2.2)
           Product: Slony-I
           Version: devel
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: low
         Component: stored procedures
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: ssinger at ca.afilias.info
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


The regression test testtruncate has stopped working in 2.2.  This test passes
on 2.1 against modern versions of postgresql.

In 2.2 I get

Truncate table "line_items" at the same time, or use TRUNCATE ... CASCADE.
CONTEXT:  SQL statement "truncate only "public"."orders""
    PL/pgSQL function _slonyregress.truncateonlytable(name) line 3 at EXECUTE
statement
    SQL statement "SELECT
"_slonyregress".TruncateOnlyTable("_slonyregress".slon_quote_brute($1) || '.'
|| "_slonyregress".slon_quote_brute($2));"
    COPY sl_log_1, line 1: "1    63744    3    584    public    orders    T   
0    {}"
STATEMENT:  COPY "_slonyregress"."sl_log_1" ( log_origin,
log_txid,log_tableid,log_actionseq,log_tablenspname, log_tablerelname,
log_cmdtype, log_cmdupdncols,log_cmdargs) FROM STDIN
ERROR:  current transaction is aborted, commands ignored until end of
transaction block


When we added TRUNCATE support to 2.1 we had it always do a TRUNCATE CASCADE.
Is there a reason why this was changed for 2.2?

-- 
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.