Excellent.
So useful getUpdateCount(), getResultSet(), and getMoreResults() return
very detailed data about each query in a statement.
Updating driver also found place we were using ps.setString(value) for a
parameter for ID = ?, and we got error asking for proper use of
ps.setInt(value).
r m wrote:
Hello
I uninstall postgresql
When I try install it again I can not do it
It requset password.
I forgot it
That is why I reinstall your software.
What should I do?
I delete all I can include ODBC system DNS registration
wild guess says you're on a Microsoft Windows system? a
On Thu, 15 Jan 2009, Raymond L. Naseef wrote:
The following bug has been logged online:
Bug reference: 4617
PostgreSQL version: 8.3 & 7.4
Operating system: FreeBSD
Description:JDBC Drivers 8.2/8.3 return no ResultSet
Details:
Below is query using temporary table instead of "I
Hello
I uninstall postgresql
When I try install it again I can not do it
It requset password.
I forgot it
That is why I reinstall your software.
What should I do?
I delete all I can include ODBC system DNS registration
Thanks,
Ruslan
Alvaro Herrera writes:
> Marshall, Steve wrote:
>> Any thoughts on how to confirm or deny Theory A?
> Try changing the 1000 to NMPWAIT_WAIT_FOREVER
As long as you're changing the source code, it'd be a good idea to
verify the supposition that kill() is failing, eg
in src/backend/commands/async.c
"Hiroshi Saito" writes:
> Operating system: Mac OS X 10.5.6
> Description:pg_ctl reports strange error message when be executed on
> non executable directory
It works all right (with some bleating) on Linux, so this seems to be
basically a deficiency of Apple's getcwd(). I really don't
Michael Fuhr writes:
> On Fri, Jan 16, 2009 at 01:22:48PM +0100, Magnus Hagander wrote:
>> I don't know where you got "with (nolock)" from, but that's not
>> PostgreSQL syntax - and AFAIK it's not standard SQL at all. Just remove
>> it and you should be fine.
> "with (nolock)" is a SQL Server-ism
Marshall, Steve wrote:
> Any thoughts on how to confirm or deny Theory A?
Try changing the 1000 to NMPWAIT_WAIT_FOREVER
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
--
Sent via pgsql-bugs ma
Tome Lane wrote:
Theory B is that you've got some broken antivirus code on there that is
arbitrarily interfering with the pipe access. The lack of any similar
previous reports suggests that there's some local issue contributing ,,,
Steve Marshall wrote:
To explore Theory B, I'll turned off all no
"Marshall, Steve" writes:
> Under a heavy load of NOTIFY events, entries in the pg_listener table
> for some events are deleted, effectively acting as though UNLISTEN
> were called.
> I have only been able to make this occur on a PostgreSQL server
> running on Windows.
"tom lane writes":
AFAIC
On Fri, Jan 16, 2009 at 01:22:48PM +0100, Magnus Hagander wrote:
> brian wrote:
> > query1 works fine, first column in table is called movieid1:
> > select * from netflix.ratings where movieid = 1
> >
> > query2 is a bug and should work just fine, but gives error:
> > ERROR: column "movieid" does
brian wrote:
> The following bug has been logged online:
>
> Bug reference: 4618
> Logged by: brian
> Email address: b4kra...@yahoo.com
> PostgreSQL version: 8.3.5 build1400
> Operating system: windows xp
> Description:nolock changes first column name of query result s
The following bug has been logged online:
Bug reference: 4618
Logged by: brian
Email address: b4kra...@yahoo.com
PostgreSQL version: 8.3.5 build1400
Operating system: windows xp
Description:nolock changes first column name of query result set to
'nolock'
Details:
q
The following bug has been logged online:
Bug reference: 4619
Logged by: Hiroshi Saito
Email address: hiroshi3...@gmail.com
PostgreSQL version: 8.3.5
Operating system: Mac OS X 10.5.6
Description:pg_ctl reports strange error message when be executed on
non executable
14 matches
Mail list logo
