On 10/24/16 9:22 AM, Petr Jelinek wrote: > I added one more prerequisite patch (the first one) which adds ephemeral > slots (or well implements UI on top of the code that was mostly already > there). The ephemeral slots are different in that they go away either on > error or when session is closed. This means the initial data sync does > not have to worry about cleaning up the slots after itself. I think this > will be useful in other places as well (for example basebackup). I > originally wanted to call them temporary slots in the UI but since the > behavior is bit different from temp tables I decided to go with what the > underlying code calls them in UI as well.
I think it makes sense to expose this. Some of the comments need some polishing. Eventually, we might want to convert the option list in CREATE_REPLICATION_SLOT into a list instead of adding more and more keywords (see also VACUUM), but not necessarily now. I find the way Acquire and Release are handled now quite confusing. Because Release of an ephemeral slot means to delete it, you have changed most code to never release them until the end of the session. So there is a lot of ugly and confusing code that needs to know this difference. I think we need to use some different verbs for different purposes here. Acquire and release should keep their meaning of "I'm using this", and the calls in proc.c and postgres.c should be something like ReplicationSlotCleanup(). -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers