@@ -6,21 +6,20 @@ given user. In order to highlight those potential issues and hopefully bring
66some sense into a confusing situation, this document was drawn.
77
88
9- client_encoding and TimeZone GUCs should be altered carefully
10- -------------------------------------------------------------
9+ client_encoding GUCs should be altered carefully
10+ ------------------------------------------------
1111
1212`postgresql.driver`'s streaming cursor implementation reads a fixed set of rows
1313when it queries the server for more. In order to optimized some situations, the
1414driver will send a request for more data, but makes no attempt to wait and
1515process the data as it is not yet needed. When the user comes back to read more
1616data from the cursor, it will then look at this new data. The problem being, if
17- the `client_encoding` or the `TimeZone` was switched, it may use the wrong codec
18- and tzinfo to transform the wire data into higher level Python objects.
17+ `client_encoding` was switched, it may use the wrong codec to transform the
18+ wire data into higher level Python objects(str) .
1919
20- To avoid this problem from ever happening, set the `TimeZone` or
21- `client_encoding` early. Furthermore, it is probably best to never change the
22- `client_encoding` as the driver automatically makes the necessary tranformation
23- to Python strings.
20+ To avoid this problem from ever happening, set the `client_encoding` early.
21+ Furthermore, it is probably best to never change the `client_encoding` as the
22+ driver automatically makes the necessary tranformation to Python strings.
2423
2524
2625The user and password is correct, but does it not work when using `postgresql.driver`
0 commit comments