If I connect do a PostgreSQL db using odbc from
windows NT client and if the password field is leaved blank the user is
successfully autenticated. :-(
Hi,
OK, having read through the list archive it appears that this problem about
users not being able to change their passwords is a problem for many people.
Has anyone come up with a good solution yet?
I may be missing something obvious here, but could a program just be written
using libpq or s
Here is a suggestion to identy your problem.
Create a very simple table with some reocrds on your old postgres, then
pgdump, and restory on your new postgres. See is there a problem? If no,
then
there must have some functions used in your old database which are different
from in the new version.
I'm running postgresql 6.5.1 on Redhat 6.0. I am trying to move a
database to a new box running 6.5.3. So I tried a 'pg_dump db_name >
db_name.out' so that I could restore the database to the new server.
The pg_dump command failed with the following error:
pqWait() -- connection not open
PQendc
Where can I find information on using indices with
a Postgres DB? In particular, I'm interested in
figuring out the implications for performance - when
is it a good idea to create an index, and under what
circumstances would it have negative consequences?
If it matters, I'm using v6.5.3 on Solari
