Age | Commit message (Collapse) | Author |
|
That case was broken in old 9.1 releases, fixed since 9.1.7.
The sequence will be owned by extension and without tagging
it will not be dumped in data dump.
|
|
|
|
|
|
Truncate events can be ignored on per handler basis.
|
|
|
|
|
|
Conflicts:
debian/changelog
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
debian/changelog
|
|
|
|
|
|
partitions" bug
|
|
|
|
|
|
partitions" bug
|
|
|
|
is from the oldest)
|
|
develop
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(in response to "londiste3 repair command floods the console with the diff mesages")
|
|
|
|
|
|
|
|
|
|
|
|
It's hard to get overview if the retry-related code
is laying around in different places.
As only Consumer class deals with retry, move all crap
into same file.
|
|
|
|
Not needed and now logutriga() behavior matches
skytools.db_urlencode() and urllib.quote_plus().
|
|
|
|
|
|
|
|
|