Sporadic "relation does not exist" errors with psqlODBC
Scott Beil <[email protected]> Tue, 11 Jul 2017 19:29:47 -0500
| Newsgroups | gmane.comp.db.postgresql.interfaces |
|---|---|
| Message-ID | <[email protected]> |
--=-TZ6nzalfmF6EGliDAkYr Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Folks, Every once in a while I get this error: ERROR: column "column_name" of relation "table_name" does not exist Here are the facts: - By every once in a while, I mean some days I get several, some days one, = some days none.=C2=A0 - The problem only occurs when under load.=C2=A0 - The database version is=C2=A09.6.3 - The problem exists in ODBC versions=C2=A009.03.0300 and=C2=A009.06.0310, = but not in=C2=A009.00.0310 (versions not mentioned have not been tested) - Two identical applications are running simultaneously. One uses 09.06.031= 0, the other uses 09.00.0310. The one using 09.06.0310 exhibits the error, = the one using 09.00.0310 does not. By the way, the app using 09.00.0310 tha= t does not produce the error is typically under a heavier load than the one= that does. - The column name in the error is one I recognize, but it belongs to anothe= r table than the one reported in the error. - To the best of my knowledge, only inserts and updates are affected. Of course the big problem here is how to reproduce or capture the problem i= n a log when it is sporadic and only occurs under load. I would like to see= this problem resolved and am willing to do my part.=C2=A0 Is producing a=C2=A0psqlodbc.log the only way to gather the required inform= ation? I'm afraid turning on logging will invoke the uncertainty principle = (not to mention blow up my hard drive!) Thanks, Scott = --=-TZ6nzalfmF6EGliDAkYr Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <html><head></head><body><div>Hi Folks,</div><div><br></div><div>Every once= in a while I get this error:</div><div><br></div><div>ERROR: column "colum= n_name" of relation "table_name" does not exist</div><div><br></div><div>He= re are the facts:</div><div><br></div><div>- By every once in a while, I me= an some days I get several, some days one, some days none. </div><div>= - The problem only occurs when under load. </div><div>- The database v= ersion is 9.6.3</div><div>- The problem exists in ODBC versions 0= 9.03.0300 and 09.06.0310, but not in 09.00.0310 (versions not men= tioned have not been tested)</div><div>- Two identical applications are run= ning simultaneously. One uses 09.06.0310, the other uses 09.00.0310. The on= e using 09.06.0310 exhibits the error, the one using 09.00.0310 does not. B= y the way, the app using 09.00.0310 that does not produce the error is typi= cally under a heavier load than the one that does.</div><div>- The column n= ame in the error is one I recognize, but it belongs to another table than t= he one reported in the error.</div><div>- To the best of my knowledge, only= inserts and updates are affected.</div><div><br></div><div>Of course the b= ig problem here is how to reproduce or capture the problem in a log when it= is sporadic and only occurs under load. I would like to see this problem r= esolved and am willing to do my part. </div><div><br></div><div>Is pro= ducing a psqlodbc.log the only way to gather the required information?= I'm afraid turning on logging will invoke the uncertainty principle (not t= o mention blow up my hard drive!)</div><div><br></div><div>Thanks,<br><br>S= cott</div><div><br></div><div><br></div><div><br></div></body></html>= --=-TZ6nzalfmF6EGliDAkYr--