> >>>>>However, a full "local" connection (without "localhost" in front of
> >
> > it)
> >
> >>>>>will block other threads (on SuperServer). On classic, it's fine.
> >>>>
> >>>>Can you be more specific ? Which operations are blocked ? Can you send
> >>>
> >>>example ?
> >>>
> >>>As far as I know, a local (IPC?) connection will block other
> >>>networked connections when doing its stuff.
> >>
> >>So, can you send some example or describe which operations are blocked ?
> >>
> >>I just did simple test - I connected to DB using local protocol
> >>and started 5 minutes long query. During that time I connected
> >>from another application using local protocol (connecion was instant),
> >>and then run simpler query, which returned result nearly immediately.
> >>Then I tried networked connection and did the same test,
> >>the connect and query were fast again (while the first application/query
> >>still running). So, what should I do to see this "blocking threads
> >>with local connection on superserver" problem ?
> >
> >
> > Well, just that :-)
> >
> > Apparently, this problem either doesn't exist anymore, doesn't manifest
> > itself as problematic anymore or my recall of theproblem has gone wild
> > and it doesn't exist.
>
> Perhaps you are talking about the InterBase 7.x client library which
> serialize the database access of multiple threads, when using a "true"
> local access?

No, I remember this from before IB 6 even... It's not blocking it's own
stuff, but others as well.

Or should I say, "supposedly blocking"

:-)

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com