up to postgresql 17, when done with a prepared statement, we could
release it with DEALLOCATE sql command which is fine ; until we want
to implement a cache solution based on statement ids.
Since PostgreSQL 17, PQclosePrepared uses internally the `close` protocol
allowing to reuse the statement name while still freeing it.
Since the close protocol implementation had been added on libpq within
this release, no way to reimplement it.
close GH-14584
There is a PostgreSQL account for the users running the test scripts
There is database named test
For instance, if your login name is testuser, you should have PostgreSQL user
account named testuser and grant that user access to the database test.
If you have account and database, type createdb test from command prompt to
create the database to execute the test scripts. By executing the above command
as the same user running the tests you ensure that the user is granted access to
the database.
If you find problems in PostgreSQL extension, please report a
bug.
1da352c367
