X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 7FAAFD1B4B4; Sat, 13 Dec 2003 10:34:34 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 84123-04; Sat, 13 Dec 2003 06:34:05 -0400 (AST) Received: from ndl1mr1-a-fixed.sancharnet.in (ndl1mr1-a-fixed.sancharnet.in [61.0.0.45]) by svr1.postgresql.org (Postfix) with ESMTP id D388DD1B462; Sat, 13 Dec 2003 06:34:01 -0400 (AST) Received: from conversion-daemon.ndl1mr1-a-fixed.sancharnet.in by ndl1mr1-a-fixed.sancharnet.in (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HPT00E01X538I@ndl1mr1-a-fixed.sancharnet.in>; Sat, 13 Dec 2003 15:59:48 +0530 (IST) Received: from sancharnet.in ([61.0.95.123]) by ndl1mr1-a-fixed.sancharnet.in (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0HPT00899X4TZ0@ndl1mr1-a-fixed.sancharnet.in>; Sat, 13 Dec 2003 15:59:48 +0530 (IST) Date: Sat, 13 Dec 2003 16:03:37 +0530 From: Sai Hertz And Control Systems Subject: Re: [PERFORM] Tables Without OIDS and its effect In-reply-to: <87he05pr8i.fsf@mailbox.samurai.com> To: Neil Conway Cc: aspire420@hotpop.com, Postgres Admin List , pgsql-performance@postgresql.org Reply-To: aspire420@hotpop.com Message-id: <3FDAEB01.3040200@sancharnet.in> Organization: Sai Hertz And Control Systems MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_xtW9LKqOugmqp3bRWinEDw)" X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 References: <3FD9E916.8050005@sancharnet.in> <87he05pr8i.fsf@mailbox.samurai.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/179 X-Sequence-Number: 11686 This is a multi-part message in MIME format. --Boundary_(ID_xtW9LKqOugmqp3bRWinEDw) Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT Hello Neil Conway, We are doing some test on our applications and will let know the community if without OIDS we could gain more speed . >>2. Though I have not written any code in my any of the pgsql functions >>which depend on OIDS >> 1. Will without OIDS the functions behave internally differently >> 2. Will my application break at any point >> >> > >No. > >BTW, we intend to phase out the use of OIDs for user tables in the >long term. There have been a few threads on -hackers that discuss the >plans for doing this. > > This was a relief for us all , but an the same time we have found one incompatibility This incompatibility is with 1. StarOffice 7.0 2. OpenOffice 1.1 and the incompatibility is when I retrieve data into Star SpreadSheet or Open Office SpreadSheet I am greeted with an error field *OID* not found. Though these both are connecting to PostgreSQL 7.3.4 (Linux GCC 3.x) via psqlODBC 07.02.0003 On the Same time WinSQL connects as usual via psqlODBC 07.02.0003 and is working fine. Though this does not effect us a lot since we are using PHP to show and retrieve data We are posting this such that any one relying totally on OpenOffice for data retrieve and display better know this , Our Test config was: -------------------------- Client :- O.S Win XP (No service pack) OpenOffice 1.1 Windows version StarOffice 7.0 Eval Pack psqlODBC 07.02.0003 Server :- OS RH 9.0 kernel-2.4.20-24.9 PostgreSQL 7.3.4 Please if anyone has a different story while using WITHOUT OIDS please let us and every one know . Regards, V Kashyap --Boundary_(ID_xtW9LKqOugmqp3bRWinEDw) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT Hello  Neil Conway,

We are doing some test on our applications and will let know the community  if without OIDS we could gain
more speed .
2. Though I have not written any code in my any of the pgsql functions
which depend on OIDS
  1. Will without OIDS the functions behave internally differently
  2. Will my application break at any point
    

No.

BTW, we intend to phase out the use of OIDs for user tables in the
long term. There have been a few threads on -hackers that discuss the
plans for doing this.
  
This was a relief  for us all , but an the same time we have found one incompatibility

This incompatibility is with
1.  StarOffice 7.0
2. OpenOffice 1.1
and the incompatibility is when I retrieve data into Star SpreadSheet or  Open Office SpreadSheet
I am greeted with an error field OID  not found.
Though these both are connecting to PostgreSQL  7.3.4 (Linux GCC 3.x) via psqlODBC  07.02.0003
On the Same time WinSQL connects as usual via psqlODBC  07.02.0003  and is working fine.

Though  this does not  effect us a lot since we are using PHP to show and retrieve data
We are posting this such that any one relying totally on OpenOffice for data  retrieve and display
better know this ,

Our Test config was:
--------------------------
Client :-
O.S           Win XP (No service pack)
OpenOffice    1.1  Windows version
StarOffice      7.0   Eval Pack
psqlODBC 07.02.0003
Server  :-
OS                      RH 9.0 kernel-2.4.20-24.9
PostgreSQL       7.3.4

Please if anyone has a different story  while using  WITHOUT  OIDS please let us and every one know .


Regards,
V Kashyap




--Boundary_(ID_xtW9LKqOugmqp3bRWinEDw)--