Marat Sharafutdinov
Marat Sharafutdinov
@zzzeek 1. Yes 2. Yes 3. Yes 4. Yes Currently 3 and 4 can be worked around by `include_object` recipe (filtering out partitioned tables by their names).
@vir-mir @asvetlov I use `aiopg.sa` and I want to use PgBouncer as a local pool on the same host instead of embedded pool, - how can I disable pooling on...
Another but not the best way (to save backward compatibility) is to mark message as processed at `done` callback of the task.
@cloud-rocket please give an example code which reproduces error.
Default value of `timeout` parameters should be some special object (`OPERATION_TIMEOUT` for example) because `None` should mean no timeout at all. ~~Will add it soon.~~ Done.
@mosquito done.
@mosquito because `wait_for` and `timeout` parameters are already inside library methods and you don't have to wrap them everywhere within your code.
Duplicate of #202.
@mosquito from pamqp's [changelog](https://github.com/gmr/pamqp/blob/master/docs/changelog.rst#300a0-2019-12-16): `Changed pamqp.decode.timestamp to return a datetime.datetime instance instead of time.struct_time.`. So I guess all helpers (`encode_timestamp` and `decode_timestamp`) can be removed, isn't it?
Any updates on this?