Undeliverable Message

To: ISMTP(at)SFRA0046@Servers[<pgsql-interfaces-digest(at)hub(dot)org>]
Cc:
Subject: pgsql-interfaces-digest V1 #291

Message not delivered to recipients below. Press F1 for help with VNM
error codes.

VNM3043: DE_VOLDER Fabrice(at)ATR_EXPL_LYON1@SFR_DO_CNTR_EST

VNM3043 -- MAILBOX IS FULL

The message cannot be delivered because the
recipient's mailbox contains the maximum number of
messages, as set by the system administrator. The
recipient must delete some messages before any
other messages can be delivered.
The maximum message limit for a user's mailbox is
10,000. The default message limit is 1000 messages.
Administrators can set message limits using the
Mailbox Settings function available in the
Manage User menu (MUSER).

When a user's mailbox reaches the limit, the
user must delete some of the messages before
the mailbox can accept any more incoming messages.

---------------------- Original Message Follows ----------------------

pgsql-interfaces-digest Thursday, March 25 1999 Volume 01 : Number 291

Index:

I can not import text file... Errno Undeliverable Message

----------------------------------------------------------------------

Date: Wed, 24 Mar 1999 22:01:28 -0800
From: Michael Irschick <mirschick(at)penguinsystems(dot)com>
Subject: I can not import text file... Errno
I have not been able to insert a text file into my postgres table.

Here is the file.
- -rw-rw-r-- 1 mirschic mirschic 14 Mar 24 21:26 test.txt
/home/mirschick/test.txt
"test","test"

- ----

oprs
ERROR: COPY command, running in backend with effective uid 100, could
not open file '/home/mirschick/test.txt' for reading. Errno Permission denied (13).
oprs
- ---

So what is going on? I tried diff text files, and diff tables I always
get the same error. (Errno
my username is mirschick
I created the text file as mirschick
I created the table, and database as mirschick.

- ---

Thanks for any help.. I am a newbie....

mirschick(at)penguinsystems(dot)com

------------------------------

Date: Thu, 25 Mar 99 7:39:31 +0100
From: <MAILER-DAEMON(at)mail1(dot)sfr(dot)fr>
Subject: Undeliverable Message

To: ISMTP(at)SFRA0046@Servers[<pgsql-interfaces-digest(at)hub(dot)org>]
Cc:
Subject: pgsql-interfaces-digest V1 #290

Message not delivered to recipients below. Press F1 for help with VNM
error codes.

VNM3043: DE_VOLDER Fabrice(at)ATR_EXPL_LYON1@SFR_DO_CNTR_EST

VNM3043 -- MAILBOX IS FULL

The message cannot be delivered because the
recipient's mailbox contains the maximum number of
messages, as set by the system administrator. The
recipient must delete some messages before any
other messages can be delivered.
The maximum message limit for a user's mailbox is
10,000. The default message limit is 1000 messages.
Administrators can set message limits using the
Mailbox Settings function available in the
Manage User menu (MUSER).

When a user's mailbox reaches the limit, the
user must delete some of the messages before
the mailbox can accept any more incoming messages.

- ---------------------- Original Message Follows ----------------------

pgsql-interfaces-digest Thursday, March 25 1999 Volume 01 : Number 290

Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 7:16:08 +0100
From: <MAILER-DAEMON(at)mail1(dot)sfr(dot)fr>
Subject: Undeliverable Message

To: ISMTP(at)SFRA0046@Servers[<pgsql-interfaces-digest(at)hub(dot)org>]
Cc:
Subject: pgsql-interfaces-digest V1 #289

Message not delivered to recipients below. Press F1 for help with VNM
error codes.

VNM3043: DE_VOLDER Fabrice(at)ATR_EXPL_LYON1@SFR_DO_CNTR_EST

VNM3043 -- MAILBOX IS FULL

The message cannot be delivered because the
recipient's mailbox contains the maximum number of
messages, as set by the system administrator. The
recipient must delete some messages before any
other messages can be delivered.
The maximum message limit for a user's mailbox is
10,000. The default message limit is 1000 messages.
Administrators can set message limits using the
Mailbox Settings function available in the
Manage User menu (MUSER).

When a user's mailbox reaches the limit, the
user must delete some of the messages before
the mailbox can accept any more incoming messages.

- - ---------------------- Original Message Follows ----------------------

pgsql-interfaces-digest Thursday, March 25 1999 Volume 01 : Number 289

Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:48:39 +0100
From: <MAILER-DAEMON(at)mail1(dot)sfr(dot)fr>
Subject: Undeliverable Message

To: ISMTP(at)SFRA0046@Servers[<pgsql-interfaces-digest(at)hub(dot)org>]
Cc:
Subject: pgsql-interfaces-digest V1 #288

Message not delivered to recipients below. Press F1 for help with VNM
error codes.

VNM3043: DE_VOLDER Fabrice(at)ATR_EXPL_LYON1@SFR_DO_CNTR_EST

VNM3043 -- MAILBOX IS FULL

The message cannot be delivered because the
recipient's mailbox contains the maximum number of
messages, as set by the system administrator. The
recipient must delete some messages before any
other messages can be delivered.
The maximum message limit for a user's mailbox is
10,000. The default message limit is 1000 messages.
Administrators can set message limits using the
Mailbox Settings function available in the
Manage User menu (MUSER).

When a user's mailbox reaches the limit, the
user must delete some of the messages before
the mailbox can accept any more incoming messages.

- - - ---------------------- Original Message Follows ----------------------

pgsql-interfaces-digest Thursday, March 25 1999 Volume 01 : Number 288

Index:

Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:30:09 +0100
From: <MAILER-DAEMON(at)mail1(dot)sfr(dot)fr>
Subject: Undeliverable Message

To: ISMTP(at)SFRA0046@Servers[<pgsql-interfaces-digest(at)hub(dot)org>]
Cc:
Subject: pgsql-interfaces-digest V1 #287

Message not delivered to recipients below. Press F1 for help with VNM
error codes.

VNM3043: DE_VOLDER Fabrice(at)ATR_EXPL_LYON1@SFR_DO_CNTR_EST

VNM3043 -- MAILBOX IS FULL

The message cannot be delivered because the
recipient's mailbox contains the maximum number of
messages, as set by the system administrator. The
recipient must delete some messages before any
other messages can be delivered.
The maximum message limit for a user's mailbox is
10,000. The default message limit is 1000 messages.
Administrators can set message limits using the
Mailbox Settings function available in the
Manage User menu (MUSER).

When a user's mailbox reaches the limit, the
user must delete some of the messages before
the mailbox can accept any more incoming messages.

- - - - ---------------------- Original Message Follows ----------------------

pgsql-interfaces-digest Wednesday, March 24 1999 Volume 01 : Number 287

Index:

Undeliverable Message

- - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:06:46 +0100
From: <MAILER-DAEMON(at)mail1(dot)sfr(dot)fr>
Subject: Undeliverable Message

To: ISMTP(at)SFRA0046@Servers[<pgsql-interfaces-digest(at)hub(dot)org>]
Cc:
Subject: pgsql-interfaces-digest V1 #286

Message not delivered to recipients below. Press F1 for help with VNM
error codes.

VNM3043: DE_VOLDER Fabrice(at)ATR_EXPL_LYON1@SFR_DO_CNTR_EST

VNM3043 -- MAILBOX IS FULL

The message cannot be delivered because the
recipient's mailbox contains the maximum number of
messages, as set by the system administrator. The
recipient must delete some messages before any
other messages can be delivered.
The maximum message limit for a user's mailbox is
10,000. The default message limit is 1000 messages.
Administrators can set message limits using the
Mailbox Settings function available in the
Manage User menu (MUSER).

When a user's mailbox reaches the limit, the
user must delete some of the messages before
the mailbox can accept any more incoming messages.

- - - - - ---------------------- Original Message Follows ----------------------

pgsql-interfaces-digest Wednesday, March 24 1999 Volume 01 : Number 286

Index:

Undeliverable Message

- - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:44:39 +0100
From: <MAILER-DAEMON(at)mail1(dot)sfr(dot)fr>
Subject: Undeliverable Message

To: ISMTP(at)SFRA0046@Servers[<pgsql-interfaces-digest(at)hub(dot)org>]
Cc:
Subject: pgsql-interfaces-digest V1 #285

Message not delivered to recipients below. Press F1 for help with VNM
error codes.

VNM3043: DE_VOLDER Fabrice(at)ATR_EXPL_LYON1@SFR_DO_CNTR_EST

VNM3043 -- MAILBOX IS FULL

The message cannot be delivered because the
recipient's mailbox contains the maximum number of
messages, as set by the system administrator. The
recipient must delete some messages before any
other messages can be delivered.
The maximum message limit for a user's mailbox is
10,000. The default message limit is 1000 messages.
Administrators can set message limits using the
Mailbox Settings function available in the
Manage User menu (MUSER).

When a user's mailbox reaches the limit, the
user must delete some of the messages before
the mailbox can accept any more incoming messages.

- - - - - - ---------------------- Original Message Follows ----------------------

pgsql-interfaces-digest Wednesday, March 24 1999 Volume 01 : Number 285

Index:

Undeliverable Message

- - - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:18:27 +0100
From: <MAILER-DAEMON(at)mail1(dot)sfr(dot)fr>
Subject: Undeliverable Message

To: ISMTP(at)SFRA0046@Servers[<pgsql-interfaces-digest(at)hub(dot)org>]
Cc:
Subject: pgsql-interfaces-digest V1 #284

Message not delivered to recipients below. Press F1 for help with VNM
error codes.

VNM3043: DE_VOLDER Fabrice(at)ATR_EXPL_LYON1@SFR_DO_CNTR_EST

VNM3043 -- MAILBOX IS FULL

The message cannot be delivered because the
recipient's mailbox contains the maximum number of
messages, as set by the system administrator. The
recipient must delete some messages before any
other messages can be delivered.
The maximum message limit for a user's mailbox is
10,000. The default message limit is 1000 messages.
Administrators can set message limits using the
Mailbox Settings function available in the
Manage User menu (MUSER).

When a user's mailbox reaches the limit, the
user must delete some of the messages before
the mailbox can accept any more incoming messages.

- - - - - - - ---------------------- Original Message Follows ----------------------

pgsql-interfaces-digest Wednesday, March 24 1999 Volume 01 : Number 284

Index:

Undeliverable Message

- - - - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 4:34:50 +0100
From: <MAILER-DAEMON(at)mail1(dot)sfr(dot)fr>
Subject: Undeliverable Message

To: ISMTP(at)SFRA0046@Servers[<pgsql-interfaces-digest(at)hub(dot)org>]
Cc:
Subject: pgsql-interfaces-digest V1 #283

Message not delivered to recipients below. Press F1 for help with VNM
error codes.

VNM3043: DE_VOLDER Fabrice(at)ATR_EXPL_LYON1@SFR_DO_CNTR_EST

VNM3043 -- MAILBOX IS FULL

The message cannot be delivered because the
recipient's mailbox contains the maximum number of
messages, as set by the system administrator. The
recipient must delete some messages before any
other messages can be delivered.
The maximum message limit for a user's mailbox is
10,000. The default message limit is 1000 messages.
Administrators can set message limits using the
Mailbox Settings function available in the
Manage User menu (MUSER).

When a user's mailbox reaches the limit, the
user must delete some of the messages before
the mailbox can accept any more incoming messages.

- - - - - - - - ---------------------- Original Message Follows ----------------------

pgsql-interfaces-digest Wednesday, March 24 1999 Volume 01 : Number 283

Index:

Undeliverable Message

- - - - - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 3:43:09 +0100
From: <MAILER-DAEMON(at)mail1(dot)sfr(dot)fr>
Subject: Undeliverable Message

To: ISMTP(at)SFRA0046@Servers[<pgsql-interfaces-digest(at)hub(dot)org>]
Cc:
Subject: pgsql-interfaces-digest V1 #282

Message not delivered to recipients below. Press F1 for help with VNM
error codes.

VNM3043: DE_VOLDER Fabrice(at)ATR_EXPL_LYON1@SFR_DO_CNTR_EST

VNM3043 -- MAILBOX IS FULL

The message cannot be delivered because the
recipient's mailbox contains the maximum number of
messages, as set by the system administrator. The
recipient must delete some messages before any
other messages can be delivered.
The maximum message limit for a user's mailbox is
10,000. The default message limit is 1000 messages.
Administrators can set message limits using the
Mailbox Settings function available in the
Manage User menu (MUSER).

When a user's mailbox reaches the limit, the
user must delete some of the messages before
the mailbox can accept any more incoming messages.

- - - - - - - - - ---------------------- Original Message Follows ----------------------

pgsql-interfaces-digest Wednesday, March 24 1999 Volume 01 : Number 282

Index:

Re: [INTERFACES] why there's only char type?
RE: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] JDBC Query performance
[ANN] pg.el -- Emacs Lisp interface for PostgreSQL
Re: [INTERFACES] Invalid BLOB Length
Re: [INTERFACES] why there's only char type?
Re: [INTERFACES] Problem using Having in a sub-query wit the Count function.
Re: [INTERFACES] Problem using Having in a sub-query wit the Count function.
[Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]
Resignation
MkLinux & ODBC compile error
pgaccess - can I tab through columns without the mouse?
Re: [INTERFACES] Resignation
radius+PAM+PostgreSQL
Re: [INTERFACES] Resignation
PgAdmin

- - - - - - - - - ----------------------------------------------------------------------

Date: Wed, 24 Mar 1999 16:03:14 -0800
From: "Daniel" <daniel(at)ids(dot)org(dot)my>
Subject: Re: [INTERFACES] why there's only char type?

This is a multi-part message in MIME format.

- - - - - - - - - - ------Content-Type: text/plain;
charsetContent-Transfer-Encoding: 7bit

After many times of reconfiguring the ODBC connection profile, recreating
the database, and even re-installing the postODBC, I think the problem lies
on the fact that Powerbuilder needs a set of its own system (or 'catalog')
tables in order to work properly in the *visual* mode. Because right now
Powerbuilder reports an error ("Catalog table could not be created and are
not available for use") everytime I start a connection to the database.
Interestingly, I could create a table with INT4 and CHAR fields from
Powerbuilder's text mode and it worked, but in visual mode, it could only
see the 1st field and ignored the 2nd.

Anyway, thanks for suggesting looking into the odbc trace log. The log files
attached with this mail created right after the following process:
1) Re-create the database test.
2) In Powerbuilder, delete & then re-configure the ODBC connection profile,
uncheck 'ReadOnly'.
3) Start the trace log (from ODBC Data Source Admin).
4) Connect to the database, and got the error msg "Catalog...." as mentioned
above.
5) Still can connect to the database. At this point if I am to create a new
table, Powerbuilder will show me only the 'char' type. But as far as the log
files are conecerned, I didnt do anything.
6) Disconnect from the database (by connecting to another db, i.e. Sybase).

If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
that a problem of PostODBC or Powerbuilder? Thanks for any help.

Daniel

- - - - - - - - - - -----Original Message-----
From: Byron Nikolaidis <byronn(at)insightdist(dot)com>
To: Daniel <daniel(at)ids(dot)org(dot)my>
Cc: pgsql-interfaces(at)hub(dot)org <pgsql-interfaces(at)hub(dot)org>
Date: Monday, March 22, 1999 11:31 AM
Subject: Re: [INTERFACES] why there's only char type?

>
>
>Daniel wrote:
>
>> Last week I got PostgreSQL 6.3.x running with -i switch and then created
a
>> test database. On Win95 end, postODBC was installed and my PowerBuilder
>> could connect to the database. Then I tried to transfer the data from
Sybase
>> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
>> Powerbuilder I did notice that there were some unfamiliar database type
in
>> Postgres such as INT4 to represent Sybase's INTEGER type and got me
really
>> excited. However I couldnt create anything in Postgres because I forgot
to
>> uncheck the "read-only" option when i setup the odbc connection, but
that's
>> different story.
>>
>> After coming back from weekend, I tried to do the transfer of data again,
>> and I did make sure the "read-only" option has been unchecked. But right
now
>> I encounter a new problem: I found that I could no longer see other data
>> type in Postgres except CHAR. I've tried all the possible setting in odbc
>> connection but it still doesn't help. What seems to be the problem?
Please
>> help.
>>
>
>I'm not sure why you would only see 'char'. If the application is using
the
>odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
>looking for data types that support a certain feature. Maybe this is
>configurable. I'm not really sure what your application is doing.
>
>If you want, you could send an odbc trace log of the session so we could at
>least see if it is calling SQLGetTypeInfo() and retrieving the results.
>Otherwise, there is nothing else I can do.
>
>Byron
>
>

- - - - - - - - - - ------Content-Type: application/octet-stream;
nameContent-Transfer-Encoding: base64
Content-Disposition: attachment;
filename
PC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBvZiBtYWlsIC0tPg0KDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRUeXBlSW5mbyANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgMCA8U1FMX0FMTF9UWVBFUz4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVYSVQgIFNRTEdldFR5cGVJbmZvICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNTKQ0K
CQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJU1dPUkQgICAgICAgICAgICAgICAg
ICAgICAgICAwIDxTUUxfQUxMX1RZUEVTPg0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRU5URVIgU1FMR2V0RnVuY3Rpb25zIA0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0
OWZmYTANCgkJVVdPUkQgICAgICAgICAgICAgICAgICAgICAgIDU5IA0KCQlVV09SRCAqICAgICAg
ICAgICAgIDB4MDA2M2UzMTYNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVY
SVQgIFNRTEdldEZ1bmN0aW9ucyAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJ
SERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCVVXT1JEICAgICAgICAgICAgICAgICAg
ICAgICA1OSANCgkJVVdPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzE2ICgxKQ0KDQpQQjA1MCAg
ICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMU2V0U3RtdE9wdGlvbiANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgOSA8U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoN
ClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxTZXRTdG10T3B0aW9u
ICB3aXRoIHJldHVybiBjb2RlIDEgKFNRTF9TVUNDRVNTX1dJVEhfSU5GTykNCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSA8
U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoNCgkJRElB
RyBbMDFTMDJdIFJlcXVlc3RlZCB2YWx1ZSBjaGFuZ2VkLjsKRHJpdmVyIGRvZXMgbm90IHN1cHBv
cnQgc2V0dGluZyB0aGlzIGNvbm5lY3Qgb3B0aW9uICgxNikgDQoNClBCMDUwICAgICAgICAgICBm
ZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAgICAgICAgICAgICAg
MHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZTJlMCAo
TllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZTMzMA0KCQlXQ0hBUiAqICAgICAg
ICAgICAgIDB4MDA2M2RlZTAgDQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAgIDUxMiANCgkJ
U1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzI2DQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2
MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUgMCAoU1FMX1NVQ0NF
U1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAg
ICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFS
ICogICAgICAgICAgICAgMHgwMDYzZTJlMCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAg
MHgwMDYzZTMzMCAoMTYpDQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZGVlMCBbICAgICAg
NzddICJSZXF1ZXN0ZWQgdmFsdWUgY2hhbmdlZC47XCBhRHJpdmVyIGRvZXMgIg0KCQlTV09SRCAg
ICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTMy
NiAoNzcpDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRT
dG10T3B0aW9uIA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAg
ICAgICAgICAgICAgICAgICAgICA5IA0KCQlQVFIgICAgICAgICAgICAgICAgMHgwMDRkZDY5Yw0K
DQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMR2V0U3RtdE9wdGlv
biAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJSFNUTVQgICAgICAgICAgICAg
ICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSANCgkJUFRSICAg
ICAgICAgICAgICAgIDB4MDA0ZGQ2OWMNCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA0ZTg5NzQgWyAgICAgNDAzXSAiQ1JFQVRFIFRBQkxF
IHBiY2F0Y29sIChwYmNfdG5hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfdGlkID8/Pz8/ICxwYmNf
b3duciBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY25hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY2lk
ID8/Pz8/ICxwYmNfbGFibCBjaGFyKDI1NCkgLHBiY19scG9zID8/Pz8/ICxwYmNfaGRyIGNoYXIo
MjU0KSAscGJjX2hwb3MgPz8/Pz8gLHBiY19qdGZ5ID8/Pz8/ICxwYmNfbWFzayBjaGFyKDMxKSAs
cGJjX2Nhc2UgPz8/Pz8gLHBiY19oZ2h0ID8/Pz8/ICxwYmNfd2R0aCA/Pz8/PyAscGJjX3B0cm4g
Y2hhcigzMSkgLHBiY19ibWFwIGNoYXIoMSkgLHBiY19pbml0IGNoYXIoMjU0KSAscGJjX2NtbnQg
Y2hhcigyNTQpICxwYmNfZWRpdCBjaGFyKDMxKSAscGJjX3RhZyBjaGFyKDI1NCkgKSINCgkJU0RX
T1JEICAgICAgICAgICAgICAgICAgIDQwMw0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRVhJVCAgU1FMRXhlY0RpcmVjdCAgd2l0aCByZXR1cm4gY29kZSAtMSAoU1FMX0VSUk9S
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVUNIQVIgKiAgICAgICAgICAg
ICAweDAwNGU4OTc0IFsgICAgIDQwM10gIkNSRUFURSBUQUJMRSBwYmNhdGNvbCAocGJjX3RuYW0g
Y2hhcigzMykgTk9UIE5VTEwscGJjX3RpZCA/Pz8/PyAscGJjX293bnIgY2hhcigzMykgTk9UIE5V
TEwscGJjX2NuYW0gY2hhcigzMykgTk9UIE5VTEwscGJjX2NpZCA/Pz8/PyAscGJjX2xhYmwgY2hh
cigyNTQpICxwYmNfbHBvcyA/Pz8/PyAscGJjX2hkciBjaGFyKDI1NCkgLHBiY19ocG9zID8/Pz8/
ICxwYmNfanRmeSA/Pz8/PyAscGJjX21hc2sgY2hhcigzMSkgLHBiY19jYXNlID8/Pz8/ICxwYmNf
aGdodCA/Pz8/PyAscGJjX3dkdGggPz8/Pz8gLHBiY19wdHJuIGNoYXIoMzEpICxwYmNfYm1hcCBj
aGFyKDEpICxwYmNfaW5pdCBjaGFyKDI1NCkgLHBiY19jbW50IGNoYXIoMjU0KSAscGJjX2VkaXQg
Y2hhcigzMSkgLHBiY190YWcgY2hhcigyNTQpICkiDQoJCVNEV09SRCAgICAgICAgICAgICAgICAg
ICA0MDMNCg0KCQlESUFHIFtTMDAwMV0gRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlOwpFUlJPUjog
IHBhcnNlcjogcGFyc2UgZXJyb3IgYXQgb3IgbmVhciAiIiAoMTcpIA0KDQpQQjA1MCAgICAgICAg
ICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMRXJyb3JXIA0KCQlIRU5WICAgICAgICAgICAg
ICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1U
ICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3
YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAgICAgIDB4MDA2M2U4MGMNCgkJV0NIQVIgKiAg
ICAgICAgICAgICAweDAwNjNlM2JjIA0KCQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIg
DQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTgwMg0KDQpQQjA1MCAgICAgICAgICAgZmZm
YjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMRXJyb3JXICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9T
VUNDRVNTKQ0KCQlIRU5WICAgICAgICAgICAgICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAg
ICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAg
ICAgIDB4MDA2M2U4MGMgKDE3KQ0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2UzYmMgWyAg
ICAgIDY3XSAiRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlO1wgYUVSUk9SOiAiDQoJCVNXT1JEICAg
ICAgICAgICAgICAgICAgICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlODAy
ICg2NykNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVOVEVSIFNRTEZyZWVT
dG10IA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAg
ICAgICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZm
ZmMyYjczCUVYSVQgIFNRTEZyZWVTdG10ICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNT
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAgICAg
ICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9u
YW1lLCBwYmVfZWRpdCwgcGJlX3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBi
ZV9mbGFnIGZyb20gcGJjYXRlZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlT
RFdPUkQgICAgICAgICAgICAgICAgICAgIC0zDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2Mzpm
ZmZjMmI3MwlFWElUICBTUUxFeGVjRGlyZWN0ICB3aXRoIHJldHVybiBjb2RlIC0xIChTUUxfRVJS
T1IpDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlVQ0hBUiAqICAgICAgICAg
ICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9uYW1lLCBwYmVfZWRpdCwgcGJl
X3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBiZV9mbGFnIGZyb20gcGJjYXRl
ZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlTRFdPUkQgICAgICAgICAgICAg
ICAgICAgIC0zDQoNCgkJRElBRyBbMDhTMDFdIEVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVl
cnk7CkVSUk9SOiAgcGJjYXRlZHQ6IFRhYmxlIGRvZXMgbm90IGV4aXN0LiAoMSkgDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAg
ICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTAN
CgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAg
MHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZjE5OA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2VkNDggDQoJCVNXT1JEICAgICAgICAgICAgICAgICAg
ICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNmMThlDQoNClBCMDUwICAgICAg
ICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUg
MCAoU1FMX1NVQ0NFU1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJD
ICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2Ew
ZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAq
ICAgICAgICAgICAgMHgwMDYzZjE5OCAoMSkNCgkJV0NIQVIgKiAgICAgICAgICAgICAweDAwNjNl
ZDQ4IFsgICAgICA3Ml0gIkVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVlcnk7XCBhRVJSIg0K
CQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAg
MHgwMDYzZjE4ZSAoNzIpDQoNCg0KPC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBv
ZiBtYWlsIC0tPg0KDQoNCg
- - - - - - - - - - ------Content-Type: application/octet-stream;
nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename
conn&282108, SQLDriverConnect( in)DSN info: DSN readonly conn_settings translation_dllconn&282108, SQLDriverConnect(out)Global Options: Version disable_optimizer_index_declarefetch
text_as_longvarchars_longvarcharools_as_char
extra_systable_prefixesconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, query [ fetched 0 rows ]
CONN ERROR: func ------------------------------------------------------------
henv'328644, conn&282108, status6
sock'328660, stmts'328700, lobj_type ---------------- Socket Info -------------------------------
socket#, reverserrornumberrrormsg buffer_in&288400, buffer_out&292500
buffer_filled_in(, buffer_filled_outuffer_read_in(
CONN ERROR: func ------------------------------------------------------------
henv'328644, conn&282108, status6
sock'328660, stmts'328700, lobj_type ---------------- Socket Info -------------------------------
socket#, reverserrornumberrrormsg buffer_in&288400, buffer_out&292500
buffer_filled_in(, buffer_filled_outuffer_read_in(
conn&282108, query [ fetched 0 rows ]
conn&282108, query [ fetched 0 rows ]
conn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryERROR from backend during send_query: 'ERROR: DefineIndex: attribute "pbt_ownr" not found'
conn&282108, querySTATEMENT ERROR: func - ------------------------------------------------------------
hdbc&282108, stmt&296600, result
manual_resultparernal
bindingsindings_allocated
parameters
rameters_allocated
statement_typeJtement stmt_with_params data_at_exec currTuple maxRowst_sizeyset_sizeursor_typeroll_concurrency
cursor_name ----------------QResult Info - -------------------------------
CONN ERROR: func ------------------------------------------------------------
henv'328644, conn&282108, status6
sock'328660, stmts'328700, lobj_type ---------------- Socket Info -------------------------------
socket#, reverserrornumberrrormsg buffer_in&288400, buffer_out&292500
buffer_filled_in+uffer_filled_outuffer_read_in
conn&282108, query [ fetched 1 rows ]
conn&282108, SQLDisconnect

- - - - - - - - - - ------
- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 08:08:45 -0000
From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Subject: RE: [INTERFACES] Converting microsoft access to postgresql

(Shameless plug!) Try pgAdmin. It is available at:

http://www.pgadmin.freeserve.co.uk

pgAdmin has a migration wizard that will copy an mdb or another ODBC
datasource table by table. It will create the table (datatypes are mapable),
copy the data if required and then create the required indexes.

Regards,

Dave.

- - - - - - - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage(at)vale-housing(dot)co(dot)uk
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!

> -----Original Message-----
> From: owner-pgsql-interfaces(at)postgreSQL(dot)org
> [mailto:owner-pgsql-interfaces(at)postgreSQL(dot)org]On Behalf Of Frederic De
> Leersnijder
> Sent: 24 March 1999 01:03
> To: pgsql-interfaces(at)postgreSQL(dot)org
> Subject: [INTERFACES] Converting microsoft access to postgresql
>
>
> I'm looking for a program to convert a microsoft access mdb
> to postgres.
>
> Thnx.
>
> Frederic De Leersnijder
>
>

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 03:07:19 -0500 (EST)
From: "Brett W. McCoy" <bmccoy(at)lan2wan(dot)com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

pgAdmin will do the job. It does it through the ODBC interface. For big
databases, though, I've had better luck dumping tables to text files and
doing a bulk copy back into PostgreSQL.

Brett W. McCoy
http://www.lan2wan.com/~bmccoy/
- - - - - - - - - - -----------------------------------------------------------------------
The Arkansas legislature passed a law that states that the Arkansas
River can rise no higher than to the Main Street bridge in Little Rock.

- - - - - - - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - - - - - - ------END GEEK CODE BLOCK------

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 03:08:34 -0500 (EST)
From: "Brett W. McCoy" <bmccoy(at)lan2wan(dot)com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

Oops. Forgot the URL for pgAdmin: http://www.pgadmin.freeserve.co.uk

Brett W. McCoy
http://www.lan2wan.com/~bmccoy/
- - - - - - - - - - -----------------------------------------------------------------------
Do not handicap your children by making their lives easy.
-- Robert Heinlein

- - - - - - - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - - - - - - ------END GEEK CODE BLOCK------

- - - - - - - - - ------------------------------

Date: Mon, 22 Mar 1999 22:51:26 -0800
From: "Postgres mailing lists" <postgres(at)weblynk(dot)com>
Subject: Re: [INTERFACES] JDBC Query performance

That's what's interesting about this to me. Using psql, piping the results
to a file, it is less than a second, and the CPU time goes to 50% idle. The
file that I piped to ends up about 3.5MB's. Jdbc is about 90 seconds, and 0%
idle. I've put trace statements in, so I'm pretty sure that to return from
the executeQuery(sql); method is about 90 seconds. If you can't reproduce
it, then maybe I could send you the table that I query, or maybe you could
send me a table that you query of similiar size (~1200 rows, 25 columns, no
indexes, most columns are varchar() or float8() ), that it performs well on.
Rich.

>Hmmm, this is interesting. Does the cpu time match when the same queries
>are run through PSQL?
>
>Peter
>
>--
>Peter T Mount, IT Section
>petermount(at)it(dot)maidstone(dot)gov(dot)uk
>Anything I write here are my own views, and cannot be taken as the
>official words of Maidstone Borough Council
>
>-----Original Message-----
>From: Postgres mailing lists [mailto:postgres(at)weblynk(dot)com]
>Sent: Sunday, March 21, 1999 7:11 PM
>To: pgsql-interfaces(at)postgreSQL(dot)org
>Subject: Re: [INTERFACES] JDBC Query performance
>
>
>>At 11:07 +0200 on 18/03/1999, Peter Mount wrote:
>>
>>
>>>
>>> The delay is because the driver currently retrieves the entire result
>>> into a Vector() before returning the ResultSet.
>>
>>Couldn't it also be because of Java's usage of network sockets compared
>to
>>psql's use of unix sockets?
>>
>You know, I also noticed that it is the postgres back-end process which
>is
>using all the CPU time during the query. Doesn't sound like Vector
>operations to me, which should cause the java process to eat all the CPU
>time.
>Rich.
>
>

- - - - - - - - - ------------------------------

Date: 24 Mar 1999 10:48:42 +0100
From: Eric Marsden <emarsden(at)mail(dot)dotcom(dot)fr>
Subject: [ANN] pg.el -- Emacs Lisp interface for PostgreSQL

pg.el is a socket-level interface to PostgreSQL for GNU Emacs (text
editor extraordinaire). The module is capable of type coercions from a
range of SQL types to the equivalent Emacs Lisp type. It currently
supports neither crypt or Kerberos authentication, nor large objects,
nor the v6.4 protocol.

The code (version 0.1) is available under GPL from

<URL:http://www.chez.com/emarsden/downloads/pg.el>

Please note that this is a programmer's API, and doesn't provide any
form of user interface. Example:

(defun demo ()
(interactive)
(let* ((conn (pg:connect "template1" "postgres" "postgres"))
(res (pg:exec conn "SELECT * from scshdemo WHERE a (message "status is %s" (pg:result res 'status))
(message "metadata is %s" (pg:result res 'attributes))
(message "data is %s" (pg:result res 'tuples))
(pg:disconnect conn)))

- - - - - - - - - - --
Eric Marsden
emarsden @ mail.dotcom.fr
It's elephants all the way down

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:35:41 -0500
From: Byron Nikolaidis <byronn(at)insightdist(dot)com>
Subject: Re: [INTERFACES] Invalid BLOB Length

PostgreSQL Server wrote:

> I am using Borland C++ Builder 3.0 with PostgreSQL 6.4.2 and the
> latest ODBC driver from ftp.postgresql.org.
>
> I created a table users that looks like this:
>
> CREATE TYPE lo (
> internallength > externallenght > input > output > send > receive > default > passedbyvalue);
>
> CREATE TABLE users (
> userid int4,
> username varchar(255),
> userimage lo);
>
> When I try and insert an image, the app returns "Invalid BLOB Length".
>
> What am I doing Wrong?
>
> Thanks
>
> Travis

Are there any errors in the driver's commlog ("psqlodbc.log") file? You
can also check the odbc trace log. If you can't figure anything out, you
can try sending me the logs and I could take a look.

Byron

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:24:28 -0500
From: Byron Nikolaidis <byronn(at)insightdist(dot)com>
Subject: Re: [INTERFACES] why there's only char type?

Daniel wrote:

> If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
> occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
> that a problem of PostODBC or Powerbuilder? Thanks for any help.
>
> Daniel
>

The below excerpt from the log I think reveals the problem. You are using an older version
of the driver (according to the psqlodbc.log -- Versionsetting the rowset size to anything greater than 1. You need to get the latest driver!
Go to http://www.insightdist.com/psqlodbc.PB050 fffb7063:fffc2b73 ENTER
SQLGetTypeInfo HSTMT 0x013a0d44
SWORD 0 <SQL_ALL_TYPES>

PB050 fffb7063:fffc2b73 EXIT SQLGetTypeInfo with return code 0 (SQL_SUCCESS)
HSTMT 0x013a0d44
SWORD 0 <SQL_ALL_TYPES>

PB050 fffb7063:fffc2b73 ENTER SQLSetStmtOption
HSTMT 0x013a0d44
UWORD 9 <SQL_ROWSET_SIZE>
UDWORD 16

PB050 fffb7063:fffc2b73 EXIT SQLSetStmtOption with return code 1
(SQL_SUCCESS_WITH_INFO)
HSTMT 0x013a0d44
UWORD 9 <SQL_ROWSET_SIZE>
UDWORD 16

DIAG [01S02] Requested value changed.;
Driver does not support setting this connect option (16)

, fetch0, socket(at)96, unknown_sizes
x_varchar_size%4, max_longvarchar_size(at)94
disable_optimizer_index_declarefetch
text_as_longvarchars_longvarcharools_as_char
extra_systable_prefixes
- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 14:25:06 +0100
From: Ordini <sferac(at)bo(dot)nettuno(dot)it>
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count function.

bug: HAVING IN SUBQUERIES
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a known bug.
Jose'

> > We are trying to execute a query that has several sub-queries embedded
> > in it. Below is a snippet of the sql code.
> >
> > "Select ordnum from ordinace where dept> > (Select ordnum from squareview where square> > ordnum from keywordview where keyword> > Gathering' group by ordnum having count(ordnum)
> >
> > The two tables in the sub-queries (squareview and keywordview) or
> > views created between two tables.
> > There are roughly about 20000 records in the keywordview view.
> >
> > When we execute the query, failing at the keywordview subquery, saying
> > the aggregate function in the having clause must appear on the right
> > side. (?) When we take the having clause out, and strictly have the
> > group by, it takes 30secs to 3mins. to return with the valid
> > recordset.
> >
> > The funny thing is, as a stand alone query on it's own, the
> > keywordview query works fine. It's very quick and has no problem with
> > the having clause.
> >
> > I was wondering if anyone else has either had this problme using
> > aggregate functions with the having clause in a subquery, or could
> > anyone give me any information of successfully executing something
> > similar to this.
> >
> > Any infomation would be appreciated.
> >
> > Thanks in advance,
> >
> > Steve
> > steve(at)ctlno(dot)com

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:54:49 -0500
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count function.

Matthew <matt(at)ctlno(dot)com> writes:
>> "Select ordnum from ordinace where dept>> (Select ordnum from squareview where square>> ordnum from keywordview where keyword>> Gathering' group by ordnum having count(ordnum)

I wonder whether the parser could be getting confused by the multiple
distinct uses of the same name "ordnum" in this query? In other words,
maybe you'd have better luck if the inner queries read something like

select
k.ordnum from keywordview k where k.keywordGathering' group by k.ordnum having count(k.ordnum)

Without that, it might be thinking that count(ordnum) refers to the
ordnum in the outer select.

If that is it, it's probably a bug, but I'm not sure what the standard
says about how to interpret ambiguous names in this context...

regards, tom lane

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 10:20:44 -0500
From: Byron Nikolaidis <byronn(at)insightdist(dot)com>
Subject: [Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]

This is a multi-part message in MIME format.
- - - - - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit

- - - - - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <36F8F7B8(dot)4A396607(at)insightdist(dot)com>
Date: Wed, 24 Mar 1999 09:33:28 -0500
From: Byron Nikolaidis <byronn(at)insightdist(dot)com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: Sam(at)OConnor(dot)net
Subject: Re: [INTERFACES] type error inserting large obj, Win32 ODBC
References: <36F5C26E(dot)49702D13(at)netspace(dot)net(dot)au> <36F679B8(dot)CF2B577C(at)insightdist(dot)com> <36F8E290(dot)73F534CF(at)netspace(dot)net(dot)au>
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit

Sam O'Connor wrote:

> I have attached the logs.
> Thankyou very much for your help.
>
> Sam O'Connor
>
>

I don't really see the problem. It seems more like there is something wrong on the postgres side.

create type lo (internallengthNxternallength,input default
If this is what you typed in to create the "lo" type, then it should work. Try inserting a row manually into the table, say something like:

insert into image ( 1, 2, 'stuff', 5);

If this fails, then maybe there is something weird with the i/o routines (int4in, int4out), in which case, you should seek more help from perhaps the "general"
mailing list.

Byron

- - - - - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9--

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:57:04 -0500
From: Byron Nikolaidis <byronn(at)insightdist(dot)com>
Subject: Resignation

Hi everyone,

I just wanted to let everyone know that today is my last day at Insight
Distribution Systems. There will be no one else at Insight taking over
the development and support of the ODBC driver since it was more of a
side project and no one knows anything about it anyway. Also, in case
anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
I was solely representing the Postgres faction at Insight.

I would like to continue my role as primary development and support of
the odbc driver to the extent possible. But since there are a lot of
factors involved, I'm just not sure what that extent might be. IF I can
keep my account at Insight, I should be able to test out things and
maybe add new functionality/features, if I have the time.

As far as the Insight-Psqlodbc web site goes, I have talked with some
people and the plan is to keep it alive. I have asked that I be allowed
to update it as necessary and they seemed agreeable to that.

I also will remain subscribed to the "interfaces" mailing list for as
long as possible (I have unsubscribed to all others). I should be able
to check the mailing list perhaps once or twice a week. I will have to
see how it goes with my new job before I know for sure. But the thing
is, since I do not currently have any internet access at home, I have to
rely on Insight to allow me to keep dialing in and doing that.

I would like to say that I have enjoyed working with everyone and I
really enjoyed contributing to the PostgreSQL project. I have learned
alot during that time and hope that I have contributed positively. I
wish everyone the best and I sincerely hope that Postgres continues to
grow at the incredible rate it has been.

Regards,

Byron

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 16:50:55 -0500
From: Mark <mlundquist(at)bvsdps(dot)com>
Subject: MkLinux & ODBC compile error

I have successfully compiled & run PostgreSQL on MkLinux many times. I
added the --with-odbc arguement and now I get an error when I compile.

misc.c:100: request for member `overflow_arg_area' in something not a structure
or union
misc.c:111: warning: passing arg 3 of `vfprintf' from incompatible pointer type
misc.c:94: warning: `args' might be used uninitialized in this function
misc.c:100: warning: `__ptr' might be used uninitialized in this function
gmake[2]: *** [misc.o] Error 1
gmake[2]: Leaving directory
`/usr/src/pgsql/postgresql-6.4.2/src/interfaces/odbc
'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/usr/src/pgsql/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2

Has anyone seen this and can help me (or anyone even reading this)?

MkLinux DR3 (RedHat Linux 5.1)
PostgreSQL 6.4.2

- - - - - - - - - - -Mark

- - - - - - - - - - -----------------------------------------------------------------
Mark Lundquist Bell Atlantic Video Services
mlundquist(at)bvsdps(dot)com 1880 Campus Commons Drive
Reston, VA 20191
- - - - - - - - - - -----------------------------------------------------------------

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 23:03:19 +0100
From: Wybo Dekker <wybo(at)servalys(dot)hobby(dot)nl>
Subject: pgaccess - can I tab through columns without the mouse?

Hi,

Normally one can jump from column to column using the tab key, but in
pgaccess this does not seem to work. Is there another way?

- - - - - - - - - - --
Hartelijke groet, Wybo Dekker
___________________Servalys Analytical Chemistry Services__________________
wybo(at)servalys(dot)hobby(dot)nl | Deilsedijk 60 | tel +31-345-652164
www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:56:15 -0300
From: Sergio <ser(at)perio(dot)unlp(dot)edu(dot)ar>
Subject: Re: [INTERFACES] Resignation

Byron Nikolaidis <byronn(at)insightdist(dot)com> el d+a Wed, 24 Mar 1999 15:57:04
- - - - - - - - - - -0500, escribi<:

>Hi everyone,
>
>I just wanted to let everyone know that today is my last day at Insight
>Distribution Systems. There will be no one else at Insight taking over
>the development and support of the ODBC driver since it was more of a
>side project and no one knows anything about it anyway. Also, in case
>anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
>I was solely representing the Postgres faction at Insight.
>
>I would like to continue my role as primary development and support of
>the odbc driver to the extent possible. But since there are a lot of
>factors involved, I'm just not sure what that extent might be. IF I can
>keep my account at Insight, I should be able to test out things and
>maybe add new functionality/features, if I have the time.
>
>As far as the Insight-Psqlodbc web site goes, I have talked with some
>people and the plan is to keep it alive. I have asked that I be allowed
>to update it as necessary and they seemed agreeable to that.
>
>I also will remain subscribed to the "interfaces" mailing list for as
>long as possible (I have unsubscribed to all others). I should be able
>to check the mailing list perhaps once or twice a week. I will have to
>see how it goes with my new job before I know for sure. But the thing
>is, since I do not currently have any internet access at home, I have to
>rely on Insight to allow me to keep dialing in and doing that.
>
>I would like to say that I have enjoyed working with everyone and I
>really enjoyed contributing to the PostgreSQL project. I have learned
>alot during that time and hope that I have contributed positively. I
>wish everyone the best and I sincerely hope that Postgres continues to
>grow at the incredible rate it has been.

Oh, my... this make my sad day...
The only thing I can do is to offer a web site (in the form of
http://perio.unlp.edu.ar/psqlodbc) that you don't have
to maintain (I will do that with whatever changes you request), but
my permanent connection to Internet is a little slow (28.8).

But, /please/, keep us informed about your movements.

Sergio

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 14:03:59 -0800
From: Matthew Hixson <hixson(at)frozenwave(dot)com>
Subject: radius+PAM+PostgreSQL

Hello,
I was wondering if anyone out there was using the Cistron radius server with
PAM support who is doing the authentication against a PostgreSQL database.
That is the setup I would like to use. However, I'm unsure of how everything
fits together.
Could someone provide me with an overview of their system, or if someone with
more of a clue than I have could explain to me how I would piece these things
together (via config files and necessary modules) I would be forever grateful.
Thanks in advance,
-M@
- - - - - - - - - - --
Matthew Hixson - CIO
FroZenWave Communications
http://www.frozenwave.com

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:16:05 -0800
From: "Ken J. Wright" <ken(at)ori-ind(dot)com>
Subject: Re: [INTERFACES] Resignation

Byron,

I, along with many others I'm sure, have come to depend greatly on your
work with the odbc driver. Your work has made PostgreSQL a viable solution
where win clients are required. Thank you and good luck with your new work!
Also, if I (or anyone else) can be of any assistance in keeping you active
here, please pipe up ;-)

Cheers!

Ken

- - - - - - - - - ------------------------------

Date: Thu, 25 Mar 1999 02:55:51 +0100
From: "Frederic De Leersnijder" <frederic(dot)de(dot)leersnijder(at)pandora(dot)be>
Subject: PgAdmin

Hi,
I'm having trouble starting PgAdmin.

I'll describe what I have done so far.

1) pgAdmin requires the PostODBC driver which is available here. You must
set check the 'Show Column' and 'Fake Index' options under 'OID Options' for
pgAdmin to work

I have installed the PostODBC driver. I haven't set show column and fake
index because I can't find the OID options.

2) As of v6.3.208, pgAdmin also requires Microsoft's MDAC 2.0 package (the
Redistribution Typical Setup version). This decreases the size of the
pgAdmin download significantly, and helps to eliminate ODBC version conflict
errors.

Done this.

3) Installing Pgadmin.

4) Opening the ODBC 32 panel in the control panel (I'm using 98)
Tab --> user dns -> MS Access driver -> configure --> database select --> In
my case h:\mediatheek.mdb

5) Starting Pgadmin

6) The logon dialog box is in front of me
datasource --> Microsoft Access 97 database.
Username: (none)
Pass: (nonea

7) The program freezes. This happens in 98 and in NT 4.0

Does someone recognize this problem?

Thnx. for the advice that will soon be on it's way (hopefully :o)) )

- - - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #282
**************************************

- - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #283
**************************************

- - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #284
**************************************

- - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #285
**************************************

- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #286
**************************************

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #287
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #288
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #289
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #290
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #291
**************************************