mirror of
https://github.com/psycopg/psycopg2.git
synced 2024-11-10 19:16:34 +03:00
Fixed notice about new wal_end attribute being on the cursor
This commit is contained in:
parent
b76ff2fc33
commit
813ca30953
2
NEWS
2
NEWS
|
@ -22,7 +22,7 @@ New features:
|
|||
C structures to Python and interact with libpq via ctypes (:ticket:`#782`).
|
||||
- `~psycopg2.sql.Identifier` can represent qualified names in SQL composition
|
||||
(:ticket:`#732`).
|
||||
- Added `!ReplicationMessage`.\ `~psycopg2.extras.ReplicationMessage.wal_end`
|
||||
- Added `!ReplicationCursor`.\ `~psycopg2.extras.ReplicationCursor.wal_end`
|
||||
attribute (:ticket:`#800`).
|
||||
- Added *fetch* parameter to `~psycopg2.extras.execute_values()` function
|
||||
(:ticket:`#813`).
|
||||
|
|
|
@ -208,8 +208,6 @@ The individual messages in the replication stream are represented by
|
|||
|
||||
LSN position of the current end of WAL on the server.
|
||||
|
||||
.. versionadded:: 2.8
|
||||
|
||||
.. attribute:: send_time
|
||||
|
||||
A `~datetime` object representing the server timestamp at the moment
|
||||
|
@ -489,6 +487,8 @@ The individual messages in the replication stream are represented by
|
|||
moment of last data or keepalive message received from the
|
||||
server.
|
||||
|
||||
.. versionadded:: 2.8
|
||||
|
||||
An actual example of asynchronous operation might look like this::
|
||||
|
||||
from select import select
|
||||
|
|
Loading…
Reference in New Issue
Block a user