There are a few usual suspects for bugs. Please look at each of these before reporting a bug:

  • Direct database access.
    • Can you reproduce the same problem in psql or some other SQL client?
    • If so, the problem probably isn't in libpqxx.
    • If you're convinced that the DBMS itself is doing the wrong thing, report it to the postgres project. Try the pgsql-general mailing list.
  • Local setup. Check your configuration etc.:
    • Are you really connecting to the database you thought you were? Is it where you expected?
    • Do you have multiple versions of libpq or libpq installed? You shouldn't, but it happens a lot. On most GNU systems, the shell command “locate libpq” will give you a list of related files.
    • Are your libpq and libpqxx installations up to date?
  • Your program. Compare what you do to what's in the libpqxx test programs and the EmployeeExample.
    • Are you doing anything that's not like anything you find in the examples?
    • Can you think of anything unusual that you're doing?
  • libpqxx. Yes, we do have bugs sometimes.

If it looks like your problem is with libpqxx, here's what you can do:

  1. Check the list of known bugs to see if the problem may already be known. Leave a comment if necessary.
  2. The bug may have been fixed in the latest development version. Try the complete list of known bugs including closed ones and the NEWS file, or try your code against the latest development snapshot.
  3. If nothing helps, enter your bug report. This can be done directly from the New Ticket button in this site's button bar. Be sure to report what libpqxx version you're having problems with; leave the milestone field blank.

When reporting a bug, do not select "AAAAA" as the applicable module. We only have that field as a trap for automated bot networks that try to post spam to the bug tracker. Also, please read about our experimental severity classification.

Last modified 8 years ago Last modified on Aug 8, 2011, 5:02:48 AM