Hello,
I already installed your extension. As of now, I'm having issues in
creating the oracle_fdw. Please advise. Thanks!
postgres=# create extension oracle_fdw;
ERROR: query plan with multiple segworker groups is not supported
HINT: likely caused by a function that reads or modifies data in
Erik Wienhold writes:
> Anyway, I prepared a patch for the docs.
I think the last hunk of this is plenty sufficient, and the earlier
ones just add noise.
regards, tom lane
On 30/08/2023 03:21 CEST Laurenz Albe wrote:
> I am somewhat surprised too, but it has been like that since commit 8ae0d476a9
> in 2005.
Yeah, unlikely to find out why after 18 years.
> The code is pretty clear about that:
>
> if (superuser == TRI_YES)
> {
> /* Not much point
I see now, any suggestions as work around in JDBC?
Thanks!!
On 9/3/23 8:12 p.m., David G. Johnston wrote:
On Sunday, September 3, 2023, Amn Ojee Uw wrote:
Are you saying that JDBC cannot handle or process \gexec, since it
is PG-15 exclusive?
psql is a client application present in
On Sunday, September 3, 2023, Amn Ojee Uw wrote:
>
> Are you saying that JDBC cannot handle or process \gexec, since it is
> PG-15 exclusive?
>
psql is a client application present in all versions of PostgreSQL. It has
a bunch of features related to executing SQL queries. The stuff that it is
On 9/3/23 15:25, Amn Ojee Uw wrote:
PD:
Are you saying that JDBC cannot handle or process \gexec, since it is
PG-15 exclusive?
I am saying \gexec is a command unique to the client program psql, it
has no meaning outside of the program. In other words it is not an SQL
command and JDBC
On Sun, Sep 3, 2023, 16:25 Amn Ojee Uw wrote:
> Are you saying that JDBC cannot handle or process \gexec, since it is
> PG-15 exclusive?
>
JDBC cannot handle our process \gexec since it is _psql_ exclusive. It's a
command interpreted and evaluated by that client specifically, not by the
Thanks Adrian, I did read the link you suggested.
I was had at the Introduction title, since it makes this mention
"/Alternatively, input can be from a file or from command line
arguments./" since the input would be from the back end of the database,
as I am using Java DBC to access the
On 9/3/23 09:00, Amn Ojee Uw wrote:
Hello!
This issue really puzzles me beyond intrigue.
Why would this schema:
*SELECT 'CREATE DATABASE jme_test_database' WHERE NOT EXISTS (SELECT
FROM pg_database WHERE datname = 'jme_test_database')\gexec*
work when entered at the psql prompt, but not when
Hello!
This issue really puzzles me beyond intrigue.
Why would this schema:
*SELECT 'CREATE DATABASE jme_test_database' WHERE NOT EXISTS (SELECT
FROM pg_database WHERE datname = 'jme_test_database')\gexec*
work when entered at the psql prompt, but not when passed as a parameter
in a JDBC
Thank you so much for the clarification.
Actually team have used similar partitioning strategy on integer columns in
past. So they are inclined towards that. I will still, double check with
others if any business restrictions exists. But as you already mentioned,
it's not good in terms of data
Have your friends also mentioned how it is going to help to convert date
field to integer !???
On Sun, Sep 3, 2023 at 3:51 AM Erik Wienhold wrote:
> On 03/09/2023 00:35 CEST veem v wrote:
>
> > We are trying to create a monthly range partition table , partitioned on
> > column PART_DATE. This
12 matches
Mail list logo
