Bugs and Feedback

For general feedback, to start and follow discussions, etc please join the veil-.nosp@m.gene.nosp@m.ral@p.nosp@m.gfou.nosp@m.ndry..nosp@m.org mailing list.

If you wish to report a bug or request a feature, please send mail to veil-.nosp@m.gene.nosp@m.ral@p.nosp@m.gfou.nosp@m.ndry..nosp@m.org

If you encounter a reproducible veil bug that causes a database server crash, a gdb backtrace would be much appreciated. To generate a backtrace, you will need to login to the postgres owner account on the database server. Then identify the postgres backend process associated with the database session that is going to crash. The following command identifies the backend pid for a database session started by marc:

$ ps auwwx | grep ^postgres.*ma[r]c | awk '{print $2}'

Now you invoke gdb with the path to the postgres binary and the pid for the backend, eg:

$ gdb /usr/lib/postgresql/9.2/bin/postgres 5444

Hit c and Enter to get gdb to allow the session to continue. Now, reproduce the crash from your database session. When the crash occurs, your gdb session will return to you. Now type bt and Enter to get a backtrace.

If you wish to contact the author offlist, you can contact him using marc@.nosp@m.bloo.nosp@m.dnok..nosp@m.com

Next: Performance