Bug 356 - TRUNCATE ONLY results in a TRUNCATE on replicas
Summary: TRUNCATE ONLY results in a TRUNCATE on replicas
Status: RESOLVED FIXED
Alias: None
Product: Slony-I
Classification: Unclassified
Component: trigger SPI (show other bugs)
Version: devel
Hardware: PC Linux
: low enhancement
Assignee: Slony Bugs List
URL:
Depends on:
Blocks:
 
Reported: 2014-12-18 11:32 UTC by Steve Singer
Modified: 2015-01-18 12:47 UTC (History)
1 user (show)

See Also:

Attachments
truncate only on replicas (1.02 KB, patch)
2014-12-18 12:38 UTC, Steve Singer 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Singer 2014-12-18 11:32:22 UTC 
This bug is in the 2.2.x series 

If you execute a 
TRUNCATE ONLY sometable;

The log trigger on 8.4+ systems will pass the truncate and perform the truncate on replicas.   However the apply function is doing

TRUNCATE someschema.sometable

which ignores the 'ONLY' causing any child tables to also get truncated.
Comment 1 Steve Singer 2014-12-18 12:38:29 UTC 
Created attachment 208 [details]
truncate only on replicas