Ravi Krishna wrote:
> On a related note is fdw for Oracle and SQLServer supported by the community ?
The PostgreSQL Global Development Group, specifically these mailing lists,
will provide support for "core PostgreSQL", that is the source code you can
download from www.postgresql.org and binaries
On 2018-10-17 11:02:40 -0700, Adrian Klaver wrote:
> On 10/17/18 10:57 AM, Ravi Krishna wrote:
> >
> > >
> > > Please note that odbc_fdw is not maintained by the postgresql developers,
> > > but a separate project.
> >
> >
> > Translation: You are on your own. We are hoping this will make our
On 10/17/18 11:12 AM, Ravi Krishna wrote:
Come on. We can't realistically support & debug random postgres extending
projects, nor do we have control over them. And you're not necessarily on your own,
you could report the issue to odbcfdw's authors/github tracker. Or pay a company
for support
Hi,
On 2018-10-17 14:12:01 -0400, Ravi Krishna wrote:
> >
> > Come on. We can't realistically support & debug random postgres extending
> > projects, nor do we have control over them. And you're not necessarily on
> > your own, you could report the issue to odbcfdw's authors/github tracker.
>
>
> Come on. We can't realistically support & debug random postgres extending
> projects, nor do we have control over them. And you're not necessarily on
> your own, you could report the issue to odbcfdw's authors/github tracker. Or
> pay a company for support.
>
On a related note is fdw for
On October 17, 2018 10:57:37 AM PDT, Ravi Krishna wrote:
>
>>
>> Please note that odbc_fdw is not maintained by the postgresql
>developers, but a separate project.
>
>
>Translation: You are on your own. We are hoping this will make our
>migration out of DB2 quicker. Oh well.
Come on. We can'
On 10/17/18 10:57 AM, Ravi Krishna wrote:
Please note that odbc_fdw is not maintained by the postgresql developers, but a
separate project.
Translation: You are on your own. We are hoping this will make our migration
out of DB2 quicker. Oh well.
No it means you need to take this up wi
>
> Please note that odbc_fdw is not maintained by the postgresql developers, but
> a separate project.
Translation: You are on your own. We are hoping this will make our migration
out of DB2 quicker. Oh well.
Hi,
On 2018-10-17 11:17:11 -0400, Ravi Krishna wrote:
> It turned out that enabling ODBC trace was causing PG to crash. Once
> disabled it started working, but found another issue.
> All object names in DB2 is assumed to be upper case. odbc_fdw sends queries
> like this
>
>
> select "fld1","
It turned out that enabling ODBC trace was causing PG to crash. Once disabled
it started working, but found another issue.
All object names in DB2 is assumed to be upper case. odbc_fdw sends queries
like this
select "fld1","fld2" from "schema_name"."table_name".
So the foreign table in PG ha
I enabled ODBC trace . Attached trace log. Had to edit connection details and
snipped few repetitive lines as I ran the same sql multiple times
Connection Out [DSN=BLUE;UID=*;PWD=***;DATABASE=***;HOST...]
[ODBC][4248][1539734369.611042][SQLGetInfo.c][554]
Entry:
11 matches
Mail list logo
