[BUGS] jdbc2 bug in absolute (ResultSet.java)
The "absolute" method is called by the relative method to change the cursor position. However, I noticed that absolute does not change current_row, it only loads the data. Shoudn't absolute contain the following line : current_row=index; Travis Bauer | CS Grad Student | IU |www.cs.indiana.edu/~trbauer
Re: [BUGS] jdbc2 bug in absolute (ResultSet.java)
You also need to remove the condition causing the procedure to return falsi if index==0. I've changed it in my code, and it fixed a few bugs that were cropping up. Travis Bauer | CS Grad Student | IU |www.cs.indiana.edu/~trbauer On Thu, 25 May 2000, Travis Bauer wrote: > The "absolute" method is called by the relative method to change the > cursor position. However, I noticed that absolute does not change > current_row, it only loads the data. > > Shoudn't absolute contain the following line : > > current_row=index; > > > Travis Bauer | CS Grad Student | IU |www.cs.indiana.edu/~trbauer > > >
Re: [BUGS] \dS and \df crashing psql
Nishad PRAKASH writes: > In psql, when connected to template1 as the postgres superuser, the > \df function complains about some memory allocation problem. The \d series of psql commands are really just shortcuts for various SQL queries to the system catalogs. Start psql with the -E option to see them. Therefore it is unlikely that this behaviour is entirely localized at these functions. Have you run the regression tests without problems? > can=# \dS > The connection to the server was lost. Attempting reset: Failed. Can you show the server output. There's probably a segmentation fault or failed assertion in the backend involved, which we'd need to see. > !# \d > You are currently not connected to a database. > !# \c can > No Postgres username specified in startup packet. > Segmentation fault That's certainly a psql problem. Can you show a backtrace from gdb? -- Peter Eisentraut Sernanders väg 10:115 [EMAIL PROTECTED] 75262 Uppsala http://yi.org/peter-e/Sweden
Re: [BUGS] \dS and \df crashing psql
On Fri, 26 May 2000, Peter Eisentraut wrote: > The \d series of psql commands are really just shortcuts for various SQL > queries to the system catalogs. Start psql with the -E option to see them. > Therefore it is unlikely that this behaviour is entirely localized at > these functions. Have you run the regression tests without problems? First of all, this was not a Postgres bug but a configuration mistake on my part. I had been meaning to write back to the list explaining what really happened: I compiled 7.0 with locale support, recode, and multibyte options all enabled. In the postgres (db superuser) .cshrc, I had set LC_CTYPE to "en_US". This was the problem. When I would start postmaster and run anything that involved a regexp (and the query that \dS expands to uses regexps) on a "bytea" type field, psql would crash. To fix this, I tried first letting the locale default to "C", then setting LC_CTYPE to "iso_8859_1". Starting postmaster with either of these works perfectly. If you are still interested in server output or backtraces (perhaps to implement a more graceful exit?), I'd be glad to send them, but I'm sure you can replicate this pretty easily now if required. I have never needed to mess around with locales before, so I apologize for posting this as bug -- I didn't quite know where to look at first. By the way, I don't know what you guys have done with the optimizer but my previously slow queries now run VERY FAST. This prevents me from taking cigarette breaks, coffee breaks, etc. under the "I'm running a large query" pretext. Please do what you can to fix this problem. Thanks for the help, Nishad
Re: [BUGS] \dS and \df crashing psql
Nishad PRAKASH <[EMAIL PROTECTED]> writes: > I compiled 7.0 with locale support, recode, and multibyte options all > enabled. In the postgres (db superuser) .cshrc, I had set LC_CTYPE to > "en_US". This was the problem. When I would start postmaster and run > anything that involved a regexp (and the query that \dS expands to uses > regexps) on a "bytea" type field, psql would crash. > To fix this, I tried first letting the locale default to "C", then setting > LC_CTYPE to "iso_8859_1". Starting postmaster with either of these works > perfectly. > If you are still interested in server output or backtraces (perhaps to > implement a more graceful exit?), I'd be glad to send them, but I'm sure > you can replicate this pretty easily now if required. Hmm, news to us. It may be a platform-specific problem, so yes please do send a backtrace. regards, tom lane
Re: [BUGS] \dS and \df crashing psql
> First of all, this was not a Postgres bug but a configuration mistake on > my part. I had been meaning to write back to the list explaining what > really happened: > > I compiled 7.0 with locale support, recode, and multibyte options all > enabled. In the postgres (db superuser) .cshrc, I had set LC_CTYPE to > "en_US". This was the problem. When I would start postmaster and run > anything that involved a regexp (and the query that \dS expands to uses > regexps) on a "bytea" type field, psql would crash. > > To fix this, I tried first letting the locale default to "C", then setting > LC_CTYPE to "iso_8859_1". Starting postmaster with either of these works > perfectly. > > If you are still interested in server output or backtraces (perhaps to > implement a more graceful exit?), I'd be glad to send them, but I'm sure > you can replicate this pretty easily now if required. Of course regexp should not crash in this situation above. Thanks for the info. I will dig into the problem. -- Tatsuo Ishii
