Hi Team,
We are doing Migration from Oracle to PostgreSQL. In SOurce database we
have Binary data stored using murmur3 hashing function. In Oracle this data
is being generated from the Java code and inserted into the Oracle
database.
As part of Migration processes the reference data on which this
Hi ALl,
Any other thought on this thread.
On Tue, Jun 21, 2022 at 2:24 PM Gilles Darold wrote:
> Le 21/06/2022 à 10:28, Jagmohan Kaintura a écrit :
>
> Hi Gilles,
>
> I was going though this earlier today but didn't compiled it as I read it
> may not be able to captur
07 PM Gilles Darold wrote:
> Le 21/06/2022 à 09:08, Jagmohan Kaintura a écrit :
>
> Hi Team,
> We are working on a project where we are moving from Oracle to PostgreSQL
> and working on a migration tool which mostly have statements for inserting
> the records which are correct an
Hi Team,
We are working on a project where we are moving from Oracle to PostgreSQL
and working on a migration tool which mostly have statements for inserting
the records which are correct and logging the errors in error table using
ORACLE inbuilt statement for INSERT ALL with DML ERROR logging.
As
:
> On Wed, 2022-02-16 at 18:10 +0530, Jagmohan Kaintura wrote:
> > We have a requirement where we wanted to keep the partitions holding the
> old data into compressed
> > format and the partition having the current data in the non-compressed
> format.
> > While looking over
Hi Team,
We have a requirement where we wanted to keep the partitions holding the
old data into compressed format and the partition having the current data
in the non-compressed format.
While looking over the compression aspects in Pg 14 we have some
compression introduced for the column level wi
Hi Team,
We are receiving alot of below error messages in the postgresql logs.
These all connections are being created and released by the applications
attached to the database.
Please help how these failures can be identified and what all steps need to
be taken for further analysis.
2021-04-08
tual data type casting rather than text for characters.
Or are there any additional index classes which we can create to overcome
this situation.
Our more focus is if we can stop from typecasting to *text and t*est how an
application behaves.
On Fri, Mar 26, 2021 at 10:38 AM Tom Lane wrote:
&
Hi All,
PostgreSQL version : 12.5
When we are compiling View definition into database , the where clause on
the Character Columns is getting internally typecasted to text.
Example : Source Code being Applied :
" FROM tms_vessel_visit_aggregate a, tms_vessel_visit v
LEFT OUTER JOIN tms_vsl_svc s
-- Forwarded message -
From: Jagmohan Kaintura
Date: Mon, Feb 22, 2021 at 7:44 AM
Subject: PostgreSQL Statement Dependency Resolving | Schema Upgrade
To:
Hi Team,
WHile performing a schema upgrade which needs any alter in the definition
of schema object, it always asks to
er accessing or viewing data to another customer. Or
Overall DBA's shouldn't be able to access sensitive data from database.
We are mostly looking over Insider Thread... Application Server
Compromise..DB server Compromise.
On Fri, Feb 12, 2021 at 1:29 AM Stephen Frost wrote:
&g
Hi Tim,
Yeh datatype is even not supported right now. As tenantId is numeric and
encryption/decryption would go through text/bytea , so even tougher to
encrypt that column data.
On Thu, Feb 11, 2021 at 7:38 AM Tim Cross wrote:
>
> Jagmohan Kaintura writes:
>
> > HI A
for one tenant, and then
> only given their ID.
> On Feb 10, 2021, 18:44 -0800, Rob Sargent , wrote:
>
>
>
> On Feb 10, 2021, at 6:45 PM, Tim Cross wrote:
>
>
> Jagmohan Kaintura writes:
>
> HI All,
>
> For POstgreSQL database to store data for multiple t
HI All,
For POstgreSQL database to store data for multiple tenants, the approach
decided was to have
Shared Database (Holding data for all tenants)
=> Data would be segregated on basis of some additional column
(tennatid,different tenants having different tenantId)
=> Data would b
Hi Team,
When we do an implementation from Oracle to PostgreSQL in trigger for
clause like :
updating(column_name) ==> (TG_OP='UPDATE' and OLD.column_name IS
DISTINCT FROM NEW.column_name)
But this condition would mostly not be sufficient when we are updating any
column and with similar val
' I came here %',v_batch_count;
v_log_count := v_log_count + 1;
v_log_count);
END;
$BODY$;
while calling
INFO: I came here 20
ERROR: invalid transaction termination
CONTEXT: PL/pgSQL function test_transaction() line 48 at COMMIT
On Tue, Nov 24, 2020 at 12:17 AM Mi
Hi ,
The Block is only failing immediately at First COMMIT only. It's not
supporting COMMIT. I have removed some portion of code before the second
COMMIT.
On Mon, Nov 23, 2020 at 9:19 PM Adrian Klaver
wrote:
> On 11/23/20 12:36 AM, Jagmohan Kaintura wrote:
> > Hi Team,
> &
Hi Team,
We have many BATCH JOBS in Oracle which we are committing after processing
few Records. These batch Jobs process in some subsets and call transaction
control statements COMMIT in case of Success and ROLLBACK in case of
failure.
While converting to POstgreSQL we converted in Same Format w
Hi Team,
I was looking for a workaround on how we can configure Failed Login
attempts feature of Oracle in PostgreSQL.
The Only requirement is End user shouldn't be allowed to Login after an "n"
number of unsuccessful attempts.
Users have the ability to perform all operations on the underlying tab
Hi All,
Since we don't have the support of Associative arrays in Postgres, we need
to convert Oracle associative arrays with a different approach in
PostgreSQL.
Following is a sample piece of code to demonstrate the same.
--Convert Oracle RECORD type to PostgreSQL TYPE.
--===
20 matches
Mail list logo
