(2013/06/12 1:26), Andres Freund wrote:
On 2013-06-11 19:20:57 +0300, Heikki Linnakangas wrote:
On 11.06.2013 19:04, Joshua Berry wrote:
Hiroshi Inoue has developed the attached patch to correct the issue that
was reported. More of the dialogue can be found in the pgsql-odbc list.
I tried
Hi,
Psqlodbc drivers send Execite requests for cursors instead of
issueing FETCH commands.
regards,
Hiroshi Inoue
(2013/05/25 1:55), Joshua Berry wrote:
Hi Groups,
I'm dealing with periodic backend process segmentation faults. I'm
posting to both the bugs and odbc lists as it see
/psqlodbc/docs/faq.html?rev=1.10&content-type=text/html
.
You can find a FAQ 6.8) Installing psqlODBC on 64bit Windows.
regards,
Hiroshi Inoue
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
x27;t list 32-bit
drivers.
regards,
Hiroshi Inoue
> Because the driver's not showing, I can't create a
data source, which is necessary to access some important internal
applications.
I've looked around on the 'net for a solution, and the only one that looked
promising (install
t;PutCollect(_T("sindex"),_...
it throws an com error that tells me "Mulit-step oper error, please check
the state value for each step "(Translated by my self from asian language)
the errmsg: Idispatch error #3015
Unfortunately I can't reproduce it here in a simple tes
the new odbc driver and you try to create a NEW odbc
connection the only available SSL mode option is disable.
Could you please try the drivers on testing for 8.4.0101 at
http://www.geocities.jp/inocchichichi/psqlodbc/index.html
?
regards,
Hiroshi Inoue
--
Sent via pgsql-bugs mailing list
Magnus Hagander wrote:
Hiroshi Inoue wrote:
Magnus Hagander wrote:
Hiroshi Inoue wrote:
Magnus Hagander wrote:
Bruce Momjian wrote:
Martin Pitt wrote:
I do see the benefit of failing to connect to an SSL-enabled server
*if* I have a root.crt which doesn't match. But why fail if I
Magnus Hagander wrote:
Hiroshi Inoue wrote:
Magnus Hagander wrote:
Bruce Momjian wrote:
Martin Pitt wrote:
I do see the benefit of failing to connect to an SSL-enabled server
*if* I have a root.crt which doesn't match. But why fail if I don't
have one?
I have digested this thread
s the snapshot psqlodbc driver already set sslverify to none and can't
change it though it may be differnet from the expected behavior. It was
not so easy to implement because sslverify parameter is illegal for <=
8.3 libpq and the psqlodbc driver doesn't rely on environment variables
a
SVC version's runtime library msvcrxx.dll.
3. Calls SetThreadLocale() if necessary.
The currently used libintl3.dll(0.14.4.1592) seems to need
this handling. ISTM it is badly built and ignores the setting
of step 2.
Description:ODBC driver 8.02.02 parses subqueries incorrectly
> Details:
>
> Problem description:
>
> the ODBC driver seems confused by suqueries. e.g.
Could you try the snapshot driver at
http://www.geocities.jp/inocchichichi/psqlodbc/index.html
?
regards,
Hiroshi In
be to install the SRX643C version
> of OpenOffice. I just heard from the [EMAIL PROTECTED] mailing list
> that the snapshot 7.03.0001 shouldn't have the bug anymore.
Oops maybe my fault sorry. Please try the snapshot.
regards,
Hiroshi Inoue
---(end of bro
> -Original Message-
> From: Ocke Janssen
>
> Hi all,
>
> when using the new PostgreSQL ODBC driver version 7.02.00.05 OpenOffice
> loops when calling SQLForeignKeys. This doesn't happen when the old
> driver 7.02.00.3 was used.
Could you send me the exam
Are you using a DO INSTEAD rule ?
Could you send me the Mylog output ?
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail co
O RecordSet from a query to Postgresql.
> When it uses MoveFirst or MoveLast to move the cursor, error
> occurs with description "Invalid Operation". Is the new version
> not supporting these method in VB?
Please try the snapshot dll at http://w2422.nsk.ne.jp/~inoue/.
regards,
Hiros
tly.
Could you send me the Mylog output ?
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
one of the cause seems the semaphore handle leak
in the cygipc library.
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
> with psqlodbc 7.01.00.09, it sends me an error 'cause the type casting {d
> > '2001-11-26'} doesn't work.
Please try the driver at
http://w2422.nsk.ne.jp/~inoue/.
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
'2001-11-26'} doesn't work.
Are you getting the following error ?
ERROR: Function 'date_part(unknown, unknown)' does not exist
Unable to identify a function that satisfies the given argument
types
You may need to add explicit typecasts
regards,
Hiroshi I
Sandor Vig wrote:
>
> Hello,
>
> I have the 6.50. ODBC driver.
It's pretty old.
Please try the latest driver at http://odbc.postgresql.org/.
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 6: Have you searched our lis
ersion of psqlodbc driver are you using ?
Could you turn on the Mylog debug output and
send me the result ?
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
eck seems to be needed in serializable
mode using the serialzable shot though I'm not sure.
currenly dead but was alive when the transaction begin
curretly alive but didin't exist when ...
etc may cause a "can't serialize ..." error.
regards,
Hiroshi I
Tom Lane wrote:
>
> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> > Currently PostgreSQL ignores the update/deleted
> > tuples from the first which don't satisfy the
> > qualification at the point of snapshot.
>
> It does? It looks to me like we use Sna
Tom Lane wrote:
>
> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> > In Mikko's both examples, Transaction 1 has to see a tuple
> > which didn't exist at the beginning of the transaction
> > while checking duplicate error.
>
> I'm not sure about t
t; is the wrong message.
PostgreSQL doesn't need to remember the preceding operations
at all in order to judge if a "can't serialize access" error
is occurred.
In Mikko's both examples, Transaction 1 has to see a tuple
which didn't exist at the beginning of the transaction
wh
r whose version >= 7.01.0006 ?
If so you could increase the size(8190) by setting MaxLongVarChar
driver option using ODBC DataSource Administarator.
You may be able to set the size to 0(unlimited?).
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
because PostgreSQL hasn't provided the proper
BLOB type. However I'm not sure now how to handle
large objects in ODBC in future.
Comments ?
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
nceid" int4 NOT NULL,
> CONSTRAINT "pk_primaryword" PRIMARY KEY ("exerciseid"),
> CONSTRAINT "fk_primaryword_significance" FOREIGN KEY
> (significanceid) REFERENCES "significance" (Significanceid) );
You aren't double quoting the c
Tom Lane wrote:
>
> "Hiroshi Inoue" <[EMAIL PROTECTED]> writes:
> > The problem is that session 2 sees a not yet deleted( by session 1)
> > session row and an already updated( by session 1) sis_user row at
> > the same time. There's no such snaps
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
>
> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> > What I meant is
> > Session 2 invokes the session_del rule and really
> > updates a sis_user row by the rule though it deletes
> &
Tom Lane wrote:
>
> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> > BTW I have a question about this example.
> > Session 2 deletes no row because *session 1* already
> > deleted the rows but the session_del rule seems to
> > be invoked. Is it a right behavior
Tom Lane wrote:
>
> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> > BTW I have a question about this example.
> > Session 2 deletes no row because *session 1* already
> > deleted the rows but the session_del rule seems to
> > be invoked. Is it a right behavior
Tom Lane wrote:
>
> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> > BTW I have a question about this example.
> > Session 2 deletes no row because *session 1* already
> > deleted the rows but the session_del rule seems to
> > be invoked. Is it a right behavior
#x27;zzz';
>
> In session 2, do:
>
> delete from session where session_key = 'zzz';
>
> Back to session 1:
>
> end;
Thanks for your quick fix as usual.
BTW I have a question about this example.
Session 2 deletes no row because *session 1* alread
be my fault, sorry.
Please try psqlodbc-07_01_0008 at
http://odbc.postgresql.org/ftpsite/odbc/versions/dll/ .
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Mika Mantyla wrote:
>
> Hiroshi Inoue wrote:
>
> > Mika Mantyla wrote:
> >
> >>Your name : Mika Ma"ntyla"
> >>
> >
> >>Your email address : [EMAIL PROTECTED]
> >>
> >>System Configuration
&g
--------
> / ParamData call /
> int
> DBStmt::ParamData( long *val )
> {
> t_usec = 0;
> do
> {
> rc = SQLParamData( hstmt, (void**)&val );
Why &val not val ?
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
C\ODBCINST.INI\PostgreSQL\Debug
as 1 to turn it on.
Note that it would generate a lot of debug output.
And never forget to turn off mylog debug, please set
the entry to 0 or remove it.
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 2: you ca
tgreSQL though it's not well known.
Psql separates it into multiple commands and call
them one by one by itself.
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
row. This seems
a bug introduced by your latest change on
pl_exec.c.
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
start. The first character position in string_exp2 is indicated by the
value 1. If string_exp1 is not found within string_exp2, the value 0 is
returned.
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
"locate" might not be the same as
> "position" :-(
>
Hmm where is locate() changed to position() ?
ISTM neither psqlodbc driver nor pg backend changes the
function call locate() to position(.. in ..).
regards,
Hiroshi Inoue
---(end of broadcast)
er
> second. After we get through several hundred thousand
> transactions, we run out of swap space on the Win2000 box. The
> Win2000 box has about 1.2 gig of swap space.
>
I've just committed a change to CVS.
It would resolve the memory leak a little.
regards,
Hiroshi Inoue
--
Tom Lane wrote:
>
> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Uh, has it ever done differently? \df certainly appears to me to list
> >> all functions in 7.0.*.
>
> > There's the following code in src/bin/pgacc
ions in 7.0.*.
>
There's the following code in src/bin/pgaccess/lib/mainlib.tcl
wpg_select $CurrentDB "select proname from pg_proc where
oid>$maxim order by proname" rec {
where maxim(the oid of "template1" database) is 1 in 7.1.
Regards,
Hiroshi Inoue
Stanislas Pinte wrote:
>
> At 06:43 PM 2/1/01 +0900, Hiroshi Inoue wrote:
> >Stanislas Pinte wrote:
> > >
> > > At 08:28 AM 2/1/01 +0900, you wrote:
> > > >Stanislas Pinte wrote:
> > > > >
> > > > > hello,
> >
e drop table doesn't work, even if the table "mytable" still appears.
> 8: I issue a "vacuumdb"...take hours, and stays blocked on my problematic table
> 9: I re-killed the back-end.
> 10: I started the DB: only four tables left...mytable and a lot of others
> have disappeared.
>
What does "select relname from pg_class;" show ?
Regards,
Hiroshi Inoue
Stanislas Pinte wrote:
>
> hello,
>
> I just had a DB crash when interrupting manually a drop table operation,
> and when interrupting manually (using kill) a vacuumdb operation. Is it
> normal, or is it a bug?
>
What does the DB crash mean ?
Regards,
Hiroshi Inoue
ugh
> and alter any actual tuples in the table, it just adds the column to the
> schema.
It seems a nice implementation.
Regards.
Hiroshi Inoue
LL description of your problem:
> >
> >
> > If declare a cursor for a query, and move with 0. Then can not
If I remember correctly *move 0* means *move all* in the
implementation of cursor.
I don't know if it's the spec or not.
> > fetch any record !
> >
>
Regards.
Hiroshi Inoue
[EMAIL PROTECTED]
50 matches
Mail list logo
