Re: Request for resolution || Support

From: Christopher Browne <cbbrowne(at)gmail(dot)com>
To: jay chauhan <jaychauhan(dot)src(at)gmail(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, suchita(dot)dudeja(at)wipro(dot)com, himanshu(dot)jayaswal1(at)wipro(dot)com
Subject: Re: Request for resolution || Support
Date: 2019-07-24 16:08:12
Message-ID: CAFNqd5UFMvZO0HS8Xc2xj7xUq3OnC2VrL7MJp=8P1=Cj3mid-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

On Wed, 24 Jul 2019 at 07:58, jay chauhan <jaychauhan(dot)src(at)gmail(dot)com> wrote:

> Hi Thomas, David/Team,
>
> Thanks you for your response. However we need your confirmation whether my
> Error/issue as mentioned below will be resolved if we upgrade our
> PostgreSQL Version.
>

No, the "issues" that you mentioned will not be automatically resolved by
upgrading to a modern version of PostgreSQL.

You will need to modify your application to use PostgreSQL facilities
properly, such as...

- Not attempting to BEGIN TRANSACTION / COMMIT WORK inside a stored
function.

Per the Fine Documentation:
https://www.postgresql.org/docs/11/plpgsql-structure.html

"Functions and trigger procedures are always executed within a transaction
established by an outer query — they cannot start or commit that
transaction, since there would be no context for them to execute in."

- ERROR: schema "utl_http" does not exist

This is a reference to some Oracle-specific thing that you would need to
reimplement in some fashion for PostgreSQL. A newer version of PostgreSQL
will not somehow draw in Oracle-proprietary features.

If you created a namespace via
create namespace utl_http;

then that particular error message would go away, but it would presumably
be replaced by some other error message as whatever it is that is missing
would still be missing.
--
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-07-24 17:06:38 Re: BUG #15922: Simple select with multiple exists filters returns duplicates from a primary key field
Previous Message David Raymond 2019-07-24 15:33:59 RE: BUG #15922: Simple select with multiple exists filters returns duplicates from a primary key field

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2019-07-24 16:11:47 Re: Default ordering option
Previous Message Cyril Champier 2019-07-24 15:22:12 Re: Default ordering option