date:20230822

Re: The same prepared query yield "-1" the first six times and then "-1.0"

2023-08-22 Thread Dave Cramer

On Tue, 22 Aug 2023 at 01:54, Edoardo Panfili  wrote:

>
>
> Il giorno 21 ago 2023, alle ore 21:37, Dave Cramer
>  ha scritto:
>
>
>
> On Mon, 21 Aug 2023 at 14:42, Edoardo Panfili  wrote:
>
>>
>>
>> > Il giorno 21 ago 2023, alle ore 20:13, Peter J. Holzer <
>> hjp-pg...@hjp.at> ha scritto:
>> >
>> > On 2023-08-21 17:27:20 +0200, Edoardo Panfili wrote:
>> >> The attended result was a sequence of ten equal values but this is the
>> actual result:
>> >> p: -1
>> >> p: -1
>> >> p: -1
>> >> p: -1
>> >> p: -1
>> >> p: -1.0
>> >> p: -1.0
>> >> p: -1.0
>> >> p: -1.0
>> >> p: -1.0
>> > [...]
>> >> 2023-08-21 11:51:50.633 CEST [1511] user@testdb LOG: execute
>> : SET extra_float_digits = 3
>> >> 2023-08-21 11:51:50.634 CEST [1511] user@testdb LOG: execute
>> : SET application_name = 'PostgreSQL JDBC Driver'
>> >> 2023-08-21 11:51:50.644 CEST [1511] user@testdb LOG: execute
>> : SELECT dim1 FROM number WHERE name='first'
>> >> 2023-08-21 11:51:50.648 CEST [1511] user@testdb LOG: execute
>> : SELECT dim1 FROM number WHERE name='first'
>> >> 2023-08-21 11:51:50.649 CEST [1511] user@testdb LOG: execute
>> : SELECT dim1 FROM number WHERE name='first'
>> >> 2023-08-21 11:51:50.650 CEST [1511] user@testdb LOG: execute
>> : SELECT dim1 FROM number WHERE name='first'
>> >> 2023-08-21 11:51:50.651 CEST [1511] user@testdb LOG: execute S_1:
>> SELECT dim1 FROM number WHERE name='first'
>> >> 2023-08-21 11:51:50.651 CEST [1511] user@testdb LOG: execute S_1:
>> SELECT dim1 FROM number WHERE name='first'
>> >> 2023-08-21 11:51:50.653 CEST [1511] user@testdb LOG: execute S_1:
>> SELECT dim1 FROM number WHERE name='first'
>> >> 2023-08-21 11:51:50.653 CEST [1511] user@testdb LOG: execute S_1:
>> SELECT dim1 FROM number WHERE name='first'
>> >> 2023-08-21 11:51:50.654 CEST [1511] user@testdb LOG: execute S_1:
>> SELECT dim1 FROM number WHERE name='first'
>> >> 2023-08-21 11:51:50.656 CEST [1511] user@testdb LOG: execute S_1:
>> SELECT dim1 FROM number WHERE name=‘first'
>> >
>> > Are these outputs from the same run?
>> Yes
>>
>> >
>> > I notice that the output from the program switches after 5 queries from
>> > "-1" to "-1-0", but the logged query name switches after 4 queries from
>> > "" to "S_1”.
>>
>> You’re right.  It seem a JDBC side problem. I am doing some tests using
>> suggestions from pgsql-jdbc list.
>>
>> What sounds strange to me is that switching from “mode_X” to  “mode_Y” I
>> obtain different representation of the same value,
>>
>> I know the value is semantically the same.. but… in some way I like to
>> see.. "a perfect postgresql env” (as it absolutely is)
>>
>> Edoardo
>>
>>
> I have confirmed that this behaviour is by design either by postgres or
> the driver. When postgres provides us the data using text mode we see -1
>
> (psql)
> select * from number ;
>  name  | dim1
> ---+--
>  first |   -1
>
> This is the way the data is presented by the text output function.
>
> And I expected to obtain the same from the JDBC connection
>
>
> In binary mode we see -1.0. This is an artifact of the binary output
> function.
>
> If ResultSet.getDouble is used the data is the same ... -1 for both text
> and binary
>
> Using getString we see the problem.
>
> So you have a few options to stop this: Set prepareThreshold to 0 and the
> driver will not switch to named statements or binary,
>
> Properties props = new Properties();
> props.setProperty("prepareThreshold", "0");
> Connection conn = DriverManager.getConnection(
> "jdbc:postgresql://192.168.64.7:5432/testdb?user=user&password=password”,
> props);
>
> Obtains “-1” all the times
>

You do give up the advantage of named statements which is that DESCRIBE
won't be necessary, but that does appear to be less of a problem than
returning a different representation.

Dave

Re: JDBC + PG-15 but not psql

2023-08-22 Thread Dave Cramer

Hi Amn,

What I don't understand is the requirement to set autocommit to true since
this is the default ?

Either way this is expected behaviour as psql also has autocommit true by
default.

Thanks,

Dave Cramer



On Mon, 21 Aug 2023 at 20:57, Amn Ojee Uw  wrote:

> Thanks Dave for your interest.
>
> In  the OP I started by explaining the difficulties when trying to create
> a tabelspace using JDBC; please note that when using the PG-15 prompt I did
> not have the problem. Well, it turns out that while developing the request
> for help (writing the email), I realize that my code had the following line
> :
> *this.conn.setAutoCommit(false);*
> However, in my research, I had read a post mentioning that by setting *auto
> commit* to *true* the issue was solved. So, I changed that line of code
> in my algorithm to :
> *this.conn.setAutoCommit(true);*
> Which also resulted in my app working without any errors.
>
> Please read the code-snip I submitted; there you can see that line of code
> I edited; which I commented with "*//** game changer!!".*
>
> Thanks again Dave, have great week.
>
>
> On 8/21/23 2:51 p.m., Dave Cramer wrote:
>
> Hi Amn,
>
> Can you help me understand this issue better?
>
> I don't see anywhere in the code where you are attempting to create a
> tablespace ?
>
>
> Dave Cramer
>
>
>
> On Sun, 20 Aug 2023 at 11:17, Amn Ojee Uw  wrote:
>
>> Hello.
>>
>> I have searched the net in an attempt to find if others have had and
>> resolved this challenge, but most of the sites talk about how, when using
>> the psql, this error arises. In my case, the error arises only when access
>> PG-15 using JDBC.
>> JDBC connects to the database, but when trying to execute a schema, it be
>> to create a database or to create a tabelspace I get this error :
>>
>> *StackTrace : [Ljava.lang.StackTraceElement;@7a69b07*
>> *Message : ERROR: CREATE TABLESPACE cannot run inside a transaction block*
>>
>> I have used the same algorithm, but now modify to accommodate PG-15, when
>> using SQLite. So the JDBC code might not be the problem, but the
>> requirements needed from PG-15.
>>
>> Change of perspective, I resolved the concern!
>>
>> Here is what changed the outcome :
>> --- snip ---
>>
>> public void connectToDatabase() throws ClassNotFoundException,
>> SQLException {
>> try {
>> Class.forName(this.getDatabaseClass().toString());
>> this.conn =
>> DriverManager.getConnection(this.getDatabaseUrl().toString(),
>> this.getUserID().toString(),
>> this.getUserPassword().toString());
>>
>> *this.conn.setAutoCommit(true);** //** game changer!!*
>>
>>
>> this.pout("Connected to the PostgreSQL server, success!!!");
>>
>> this.stmt = this.conn.createStatement();
>> } catch (final SQLException | ClassNotFoundException e) {
>> throw e;
>> }
>> }
>>
>> --
>>
>> All I had to do was to setAutoCommit to true, PG-15 set this value to
>> false by default.
>>
>>
>> I hope my experience can help others.
>>
>>
>>

Released vasco: a PG extension to compute MIC and MINE correlation statistics

2023-08-22 Thread Florents Tselai

Hello,

If you're looking for a more powerful alternative to corr(X, Y), I just
open - sourced an vasco [0]

vasco is a Postgres extension that helps you discover hidden correlations
in your data. It is based on the MIC and MINE family of statistics.

[0] https://github.com/Florents-Tselai/vasco

Re: JDBC + PG-15 but not psql

2023-08-22 Thread Amn Ojee Uw

Yes your are right! I don't know why it was part of the requirement to 
add a JDBC line to explicitly set the behaviour of autocommint to 
*true*, when it was the default value. Perhaps it has to do with "just 
making sure it is" sort of thing.

Thanks Dave, I'll let the my group know.

On 8/22/23 8:31 a.m., Dave Cramer wrote:

Hi Amn,

What I don't understand is the requirement to set autocommit to true 
since this is the default ?


Either way this is expected behaviour as psql also has autocommit true 
by default.


Thanks,

Dave Cramer



On Mon, 21 Aug 2023 at 20:57, Amn Ojee Uw  wrote:

Thanks Dave for your interest.

In  the OP I started by explaining the difficulties when trying to
create a tabelspace using JDBC; please note that when using the
PG-15 prompt I did not have the problem. Well, it turns out that
while developing the request for help (writing the email), I
realize that my code had the following line :
*this.conn.setAutoCommit(false);*/*
*/However, in my research, I had read a post mentioning that by
setting /auto commit/ to *true* the issue was solved. So, I
changed that line of code in my algorithm to :
*this.conn.setAutoCommit(true);*/*
*/Which also resulted in my app working without any errors./**/

Please read the code-snip I submitted; there you can see that line
of code I edited; which I commented with "/*//*//*game changer!!".*/

Thanks again Dave, have great week.

/*
*/

On 8/21/23 2:51 p.m., Dave Cramer wrote:

Hi Amn,

Can you help me understand this issue better?

I don't see anywhere in the code where you are attempting to
create a tablespace ?


Dave Cramer



On Sun, 20 Aug 2023 at 11:17, Amn Ojee Uw 
wrote:

Hello.

I have searched the net in an attempt to find if others have
had and resolved this challenge, but most of the sites talk
about how, when using the psql, this error arises. In my
case, the error arises only when access PG-15 using JDBC.
JDBC connects to the database, but when trying to execute a
schema, it be to create a database or to create a tabelspace
I get this error :

*StackTrace : [Ljava.lang.StackTraceElement;@7a69b07**
**Message : ERROR: CREATE TABLESPACE cannot run inside a
transaction block*

I have used the same algorithm, but now modify to accommodate
PG-15, when using SQLite. So the JDBC code might not be the
problem, but the requirements needed from PG-15.

Change of perspective, I resolved the concern!

Here is what changed the outcome :
--- snip ---

public void connectToDatabase() throws
ClassNotFoundException, SQLException {
    try {
Class.forName(this.getDatabaseClass().toString());
    this.conn =
DriverManager.getConnection(this.getDatabaseUrl().toString(),
    this.getUserID().toString(),
this.getUserPassword().toString());

*this.conn.setAutoCommit(true);*/*//*//*game changer!!*/

        this.pout("Connected to the PostgreSQL server,
success!!!");

    this.stmt = this.conn.createStatement();
    } catch (final SQLException | ClassNotFoundException e) {
    throw e;
    }
}

--

All I had to do was to setAutoCommit to true, PG-15 set this
value to false by default.


I hope my experience can help others.

Oracle FDW version

2023-08-22 Thread Jethro Elmer Sanidad

Hello,

Can you provide us download links for oracle_fdw for psql (PostgreSQL)
9.4.24. Currently, we can't find oracle_fdw that will be compatible to the
said PostgreSQL version. Per chatGPT, the oracle_fdw version should be
1.8.1 for the said PostgreSQL version.  We already checked in laurenz's
github but there is no oracle_fdw version 1.8.1 in his repository. Thanks!

-- 

[image: image.png] 

*Jethro Elmer T. Sanidad*
Management Information Systems
O: +63 2 8889 8890 loc. 1354 | M: +63 9686809253
Gardenia Bakeries Philippines Incorporated | Laguna International
Industrial Park (LIIP) | Binan 4024 | Laguna

-- 






















*CONFIDENTIALITY NOTICE:* This email is
confidential 
and subject to legal rights of Gardenia Bakeries (Philippines),
Inc. 
(“GBPI”). If you received this email by error, you must not use or
disclose 
any information in it and immediately notify the sender by return
email and 
permanently delete this email (and all attachments) without any use
of its 
contents. To the extent legally permitted, GBPI has no liability of any
kind arising out of or in connection with any virus transmitted by this 
email,
attachments, and/or any errors or omissions in content including 
transmissions
through unauthorised use or tampering of email system and/or 
the integrity of the email
being compromised. Any personal statements or
opinions in this communication are those of the individual sender and do 
not
reflect the views of GBPI. GBPI will never consent to
or authorize the 
publication of defamatory statements or infringement of
intellectual 
property. Only individuals authorized by GBPI’s Board of Directors
may sign 
and/or accept proposals, contracts, or agreements as well as waive any
legal right of GBPI. Any personal information in this email must be handled 
in
accordance with the Data Privacy Act of 2012 of the Philippines and its
implementing rules and regulations.

Re: Oracle FDW version

2023-08-22 Thread Tom Lane

Jethro Elmer Sanidad  writes:
> Can you provide us download links for oracle_fdw for psql (PostgreSQL)
> 9.4.24.

PG 9.4.x has been out of support since 2020 [1].  You need to be
looking to upgrade that server to something that's in support, and
then you can probably find a matching in-support oracle_fdw version.

regards, tom lane

[1] https://www.postgresql.org/support/versioning/

Re: Oracle FDW version

2023-08-22 Thread Adrian Klaver


On 8/22/23 19:25, Jethro Elmer Sanidad wrote:

Hello,

Can you provide us download links for oracle_fdw for psql (PostgreSQL) 
9.4.24. Currently, we can't find oracle_fdw that will be compatible to 
the said PostgreSQL version. Per chatGPT, the oracle_fdw version should 
be 1.8.1 for the said PostgreSQL version.  We already checked in 


From what I see ChatGPT is making things up again.

If you go here:

https://github.com/laurenz/oracle_fdw

the tags go from:

https://github.com/laurenz/oracle_fdw/tree/ORACLE_FDW_1_5_0

to

https://github.com/laurenz/oracle_fdw/tree/ORACLE_FDW_2_0_0

Personally I would try the 2.0 version. That came out(2017-09-15) in the 
middle of 9.4's life span(9.4 	9.4.26 	No 	December 18, 2014 	February 
13, 2020).



laurenz's github but there is no oracle_fdw version 1.8.1 in his 
repository. Thanks!


--

image.png 

*Jethro Elmer T. Sanidad*
Management Information Systems
O: +63 2 8889 8890 loc. 1354 | M: +63 9686809253
Gardenia Bakeries Philippines Incorporated | Laguna International 
Industrial Park (LIIP) | Binan 4024 | Laguna



*CONFIDENTIALITY NOTICE:* This email is confidential and subject to 
legal rights of Gardenia Bakeries (Philippines), Inc. (“GBPI”). If you 
received this email by error, you must not use or disclose any 
information in it and immediately notify the sender by return email and 
permanently delete this email (and all attachments) without any use of 
its contents. To the extent legally permitted, GBPI has no liability of 
any kind arising out of or in connection with any virus transmitted by 
this email, attachments, and/or any errors or omissions in content 
including transmissions through unauthorised use or tampering of email 
system and/or theintegrity of the email being compromised. Any personal 
statements or opinions in this communication are those of the individual 
sender and do not reflect the views of GBPI. GBPI will never consent to 
or authorize the publication of defamatory statements or infringement of 
intellectual property. Only individuals authorized by GBPI’s Board of 
Directors may sign and/or accept proposals, contracts, or agreements as 
well as waive any legal right of GBPI. Any personal information in this 
email must be handled in accordance with the Data Privacy Act of 2012 of 
the Philippines and its implementing rules and regulations.




--
Adrian Klaver
adrian.kla...@aklaver.com

Re: [EXTERNAL] Re: Oracle FDW version

2023-08-22 Thread Jethro Elmer Sanidad

Hello,

I tried both the 1.5.0 and 2.0.0. Both returned error during 'make'
command. Please see below:



[gpadmin@gbpi-fmstr-uat-danalytics-01 oracle_fdw-ORACLE_FDW_2_0_0]$ make
gcc -m64 -Wall -Wmissing-prototypes -Wpointer-arith -Wendif-labels
-Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv
-fexcess-precision=standard -fno-aggressive-loop-optimizations
-Wno-unused-but-set-variable -Wno-address -m64 -O3
-fargument-noalias-global -fno-omit-frame-pointer -g -std=gnu99
-Werror=uninitialized -Werror=implicit-function-declaration -fPIC
-I/sdk/include -I/oci/include -I/rdbms/public
-I/usr/include/oracle/12.2/client -I/usr/include/oracle/12.2/client64
-I/usr/include/oracle/12.1/client -I/usr/include/oracle/12.1/client64
-I/usr/include/oracle/11.2/client -I/usr/include/oracle/11.2/client64
-I/usr/include/oracle/11.1/client -I/usr/include/oracle/11.1/client64
-I/usr/include/oracle/10.2.0.5/client -I/usr/include/oracle/
10.2.0.5/client64 -I/usr/include/oracle/10.2.0.4/client
-I/usr/include/oracle/10.2.0.4/client64 -I/usr/include/oracle/
10.2.0.3/client -I/usr/include/oracle/10.2.0.3/client64 -I. -I./
-I/usr/local/greenplum-db-6.7.1/include/postgresql/server
-I/usr/local/greenplum-db-6.7.1/include/postgresql/internal -D_GNU_SOURCE
-I/usr/include/libxml2
 -I/tmp/build/f8c7ee08/gpdb_src/gpAux/ext/rhel7_x86_64/include  -c -o
oracle_fdw.o oracle_fdw.c
oracle_fdw.c: In function ‘oracleGetForeignRelSize’:
oracle_fdw.c:884:3: error: too few arguments to function
‘clauselist_selectivity’
   ntuples = ntuples * clauselist_selectivity(root,
baserel->baserestrictinfo, 0, JOIN_INNER, NULL);
   ^
In file included from oracle_fdw.c:48:0:
/usr/local/greenplum-db-6.7.1/include/postgresql/server/optimizer/cost.h:225:20:
note: declared here
 extern Selectivity clauselist_selectivity(PlannerInfo *root,
^
oracle_fdw.c: In function ‘oracleIterateForeignScan’:
oracle_fdw.c:1445:31: error: ‘TupleTableSlot’ has no member named
‘tts_values’
   convertTuple(fdw_state, slot->tts_values, slot->tts_isnull, false);
   ^
oracle_fdw.c:1445:49: error: ‘TupleTableSlot’ has no member named
‘tts_isnull’
   convertTuple(fdw_state, slot->tts_values, slot->tts_isnull, false);
 ^
oracle_fdw.c: In function ‘oracleExecForeignInsert’:
oracle_fdw.c:2044:30: error: ‘TupleTableSlot’ has no member named
‘tts_values’
  convertTuple(fdw_state, slot->tts_values, slot->tts_isnull, false);
  ^
oracle_fdw.c:2044:48: error: ‘TupleTableSlot’ has no member named
‘tts_isnull’
  convertTuple(fdw_state, slot->tts_values, slot->tts_isnull, false);
^
oracle_fdw.c: In function ‘oracleExecForeignUpdate’:
oracle_fdw.c:2090:30: error: ‘TupleTableSlot’ has no member named
‘tts_values’
  convertTuple(fdw_state, slot->tts_values, slot->tts_isnull, false);
  ^
oracle_fdw.c:2090:48: error: ‘TupleTableSlot’ has no member named
‘tts_isnull’
  convertTuple(fdw_state, slot->tts_values, slot->tts_isnull, false);
^
oracle_fdw.c: In function ‘oracleExecForeignDelete’:
oracle_fdw.c:2136:30: error: ‘TupleTableSlot’ has no member named
‘tts_values’
  convertTuple(fdw_state, slot->tts_values, slot->tts_isnull, false);
  ^
oracle_fdw.c:2136:48: error: ‘TupleTableSlot’ has no member named
‘tts_isnull’
  convertTuple(fdw_state, slot->tts_values, slot->tts_isnull, false);
^
make: *** [oracle_fdw.o] Error 1

---

[gpadmin@gbpi-fmstr-uat-danalytics-01 oracle_fdw-ORACLE_FDW_1_5_0]$ make
gcc -m64 -Wall -Wmissing-prototypes -Wpointer-arith -Wendif-labels
-Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv
-fexcess-precision=standard -fno-aggressive-loop-optimizations
-Wno-unused-but-set-variable -Wno-address -m64 -O3
-fargument-noalias-global -fno-omit-frame-pointer -g -std=gnu99
-Werror=uninitialized -Werror=implicit-function-declaration -fPIC
-I/sdk/include -I/oci/include -I/rdbms/public
-I/usr/include/oracle/12.1/client -I/usr/include/oracle/12.1/client64
-I/usr/include/oracle/11.2/client -I/usr/include/oracle/11.2/client64
-I/usr/include/oracle/11.1/client -I/usr/include/oracle/11.1/client64
-I/usr/include/oracle/10.2.0.5/client -I/usr/include/oracle/
10.2.0.5/client64 -I/usr/include/oracle/10.2.0.4/client
-I/usr/include/oracle/10.2.0.4/client64 -I/usr/include/oracle/
10.2.0.3/client -I/usr/include/oracle/10.2.0.3/client64 -I. -I./
-I/usr/local/greenplum-db-6.7.1/include/postgresql/server
-I/usr/local/greenplum-db-6.7.1/include/postgresql/internal -D_GN

Re: [EXTERNAL] Re: Oracle FDW version

2023-08-22 Thread Tom Lane

Jethro Elmer Sanidad  writes:
> I tried both the 1.5.0 and 2.0.0. Both returned error during 'make'
> command. Please see below:

So evidently,

> oracle_fdw.c: In function ‘oracleGetForeignRelSize’:
> oracle_fdw.c:884:3: error: too few arguments to function 
> ‘clauselist_selectivity’
>ntuples = ntuples * clauselist_selectivity(root, 
> baserel->baserestrictinfo, 0, JOIN_INNER, NULL);
> In file included from oracle_fdw.c:48:0:
> /usr/local/greenplum-db-6.7.1/include/postgresql/server/optimizer/cost.h:225:20:
> note: declared here

your compatibility problem is not with Postgres 9.4.x at all, but with
some version of Greenplum.  (Aside from the giveaway include path, no
extant version of community Postgres has a cost.h file that is as much
as 225 lines long, nor do we expect clauselist_selectivity to take
more than five arguments.)  Please speak to Greenplum customer
support, rather than expecting the wider Postgres community to help
you for free with a code base that we don't even know.

regards, tom lane

Re: [EXTERNAL] Oracle FDW version

2023-08-22 Thread Christophe Pettus

> On Aug 22, 2023, at 19:57, Jethro Elmer Sanidad 
>  wrote:
> 
> Hello,
> 
> I tried both the 1.5.0 and 2.0.0. Both returned error during 'make' command. 
> Please see below:

The API between PostgreSQL and foreign data wrappers has changed significantly 
since 9.4.  As Tom mentioned, you need to upgrade your server to something 
in-support.

Re: [EXTERNAL] Oracle FDW version

2023-08-22 Thread Ian Lawrence Barwick

2023年8月23日(水) 12:47 Christophe Pettus :
>
>
>
> > On Aug 22, 2023, at 19:57, Jethro Elmer Sanidad 
> >  wrote:
> >
> > Hello,
> >
> > I tried both the 1.5.0 and 2.0.0. Both returned error during 'make' 
> > command. Please see below:
>
> The API between PostgreSQL and foreign data wrappers has changed 
> significantly since 9.4.  As Tom mentioned, you need to upgrade your server 
> to something in-support.

FWIW oracle_fdw should actually build against PostgreSQL as far back as 9.3
(though finding packages would be a fruitless endeavour); the documentation
does explicitly mention that it will likely not build against forks which are
not compatible with the community code [1].

[1] https://github.com/laurenz/oracle_fdw#5-installation-requirements

Regards

Ian Barwick

Re: [EXTERNAL] Oracle FDW version

2023-08-22 Thread Jethro Elmer Sanidad

Hello,

Can you confirm in this email that our current version of PostgreSQL
(9.2.24) is not compatible with any of oracle_fdw versions released? And
you are recommending an upgrade? Thanks!

On Wed, Aug 23, 2023 at 2:04 PM Ian Lawrence Barwick 
wrote:

> 2023年8月23日(水) 12:47 Christophe Pettus :
> >
> >
> >
> > > On Aug 22, 2023, at 19:57, Jethro Elmer Sanidad <
> jethroelmersani...@gardenia.com.ph> wrote:
> > >
> > > Hello,
> > >
> > > I tried both the 1.5.0 and 2.0.0. Both returned error during 'make'
> command. Please see below:
> >
> > The API between PostgreSQL and foreign data wrappers has changed
> significantly since 9.4.  As Tom mentioned, you need to upgrade your server
> to something in-support.
>
> FWIW oracle_fdw should actually build against PostgreSQL as far back as 9.3
> (though finding packages would be a fruitless endeavour); the documentation
> does explicitly mention that it will likely not build against forks which
> are
> not compatible with the community code [1].
>
> [1] https://github.com/laurenz/oracle_fdw#5-installation-requirements
>
> Regards
>
> Ian Barwick
>

-- 

[image: image.png] 

*Jethro Elmer T. Sanidad*
Management Information Systems
O: +63 2 8889 8890 loc. 1354 | M: +63 9686809253
Gardenia Bakeries Philippines Incorporated | Laguna International
Industrial Park (LIIP) | Binan 4024 | Laguna

-- 

*CONFIDENTIALITY NOTICE:* This email is
confidential 
and subject to legal rights of Gardenia Bakeries (Philippines),
Inc. 
(“GBPI”). If you received this email by error, you must not use or
disclose 
any information in it and immediately notify the sender by return
email and 
permanently delete this email (and all attachments) without any use
of its 
contents. To the extent legally permitted, GBPI has no liability of any
kind arising out of or in connection with any virus transmitted by this 
email,
attachments, and/or any errors or omissions in content including 
transmissions
through unauthorised use or tampering of email system and/or 
the integrity of the email
being compromised. Any personal statements or
opinions in this communication are those of the individual sender and do 
not
reflect the views of GBPI. GBPI will never consent to
or authorize the 
publication of defamatory statements or infringement of
intellectual 
property. Only individuals authorized by GBPI’s Board of Directors
may sign 
and/or accept proposals, contracts, or agreements as well as waive any
legal right of GBPI. Any personal information in this email must be handled 
in
accordance with the Data Privacy Act of 2012 of the Philippines and its
implementing rules and regulations.

Re: [EXTERNAL] Oracle FDW version

2023-08-22 Thread Justin Clift


On 2023-08-23 16:10, Jethro Elmer Sanidad wrote:

Hello,

Can you confirm in this email that our current version of PostgreSQL
(9.2.24) is not compatible with any of oracle_fdw versions released? 
And

you are recommending an upgrade? Thanks!


It seems more like you're not actually using PostgreSQL, but are instead
using a special proprietary spin-off called Greenplum.

If that's the case, then you'll need to have a chat with the Greenplum
support people.  They'll know their product better than we do. :)

Regards and best wishes,

Justin Clift

Re: The same prepared query yield "-1" the first six times and then "-1.0"

Re: JDBC + PG-15 but not psql

Released vasco: a PG extension to compute MIC and MINE correlation statistics

Re: JDBC + PG-15 but not psql

Oracle FDW version

Re: Oracle FDW version

Re: Oracle FDW version

Re: [EXTERNAL] Re: Oracle FDW version

Re: [EXTERNAL] Re: Oracle FDW version

Re: [EXTERNAL] Oracle FDW version

Re: [EXTERNAL] Oracle FDW version

Re: [EXTERNAL] Oracle FDW version

Re: [EXTERNAL] Oracle FDW version

13 matches

Site Navigation

Mail list logo

Footer information