Selena Deckelmann selenamarie at gmail.com
Thu Aug 19 11:14:36 PDT 2010
On Thu, Aug 19, 2010 at 11:21 AM, Jan Wieck <JanWieck at yahoo.com> wrote:
> On 8/18/2010 9:40 PM, Christopher Browne wrote:
>> Where Jan's leaning comes in the comment here:
>> ------
>> To fix this, slonik needs to issue LOCK TABLE statements right after "begin;".
>> That way, it will wait until all conflicting transactions have committed before
>> generating its own snapshot.
>>
>> We need new syntax to add this information to the EXECUTE SCRIPT command and it
>> will be the responsibility of the user to provide the list of tables to lock.
>
> An alternative to this would be to have EXECUTE SCRIPT parse the DDL
> script a little deeper, executing all LOCK TABLE statements at the
> beginning, before creating the SYNC that contains all DML before the DDL.
>
> This way we would not need to change the EXECUTE SCRIPT syntax at all.

That was the suggestion I was going to make!

Its sort of the inverse of how the executor treats EXPLAIN.. maybe? :)

-selena


-- 
http://chesnok.com/daily - me


More information about the Slony1-general mailing list