On 2024-05-02 13:24, Bagesh kamar singh wrote:
Recently we migrated our postgreSQL single server to flexi server.
Hmmm, what's "Flexi server"?
Doing a quick online search just now isn't showing things that seem
to be PostgreSQL related.
Regards and best wishes,
Justin Clift
On Thu, May 2, 2024 at 8:28 PM Amit Sharma wrote:
> Hello,
>
> Has anyone tried delta/incremental data migration for Oracle to PostgreSQL
> using Ora2pg? Or what are the best options to run delta migration for
> Oracle to PostgreSQL?
>
What do the ora2pg docs say about whether or not that
I did the testing and confirmed that this was the issue.
I run following query:
create table t as select '1234567890' from generate_series(1, 10);
I commented if (numblocks > 8) codeblock, and see the following results
from "compsize /dbdir/" command.
Before my changes:
Processed
Hello,
Has anyone tried delta/incremental data migration for Oracle to PostgreSQL
using Ora2pg? Or what are the best options to run delta migration for
Oracle to PostgreSQL?
Thanks
Amit
On 5/2/24 08:52, HORDER Philip wrote:
Running Postgres 15.3 with PostGIS 3.3
On Windows 10 (yes, I know)
It’s a single node db with no replication, topping out at about 200GB.
We have a schema (A) in the default 'postgres' maintenance database,
which our software services connect to, with
On 5/2/24 8:52 AM, HORDER Philip wrote:
Running Postgres 15.3 with PostGIS 3.3
On Windows 10 (yes, I know)
It’s a single node db with no replication, topping out at about 200GB.
We have a schema (A) in the default 'postgres' maintenance database,
which our software services connect to,
Running Postgres 15.3 with PostGIS 3.3
On Windows 10 (yes, I know)
It's a single node db with no replication, topping out at about 200GB.
We have a schema (A) in the default 'postgres' maintenance database, which our
software services connect to, with one set of users (SU)
We have another
On 5/2/24 02:20, Fire Emerald wrote:
I didn't used pg_dump/restore until today and finally found my mistake
which lead to the "problem" described below.
The output "depends on" comes from the -l (l as Lima) flag, what i
wanted was the -1 (number one) flag, which stands for single transaction
Thom Brown writes:
> On Thu, 2 May 2024 at 12:40, Durumdara wrote:
>> Do you have a working Query which lists the user defined types with the
>> owners?
> You can always cheat and copy what psql does when you tell it to list all
> user types with extended output (\dt+):
If you want to look at
On Thu, May 2, 2024 at 1:47 AM RAJAMOHAN wrote:
> Hello all,
>
> In our production db infrastructure, we have one read_only role which has
> read privileges against all tables in schema A.
>
> We are planning to grant this role to some developers for viewing the
> data, but also I want to limit
On Thu, 2 May 2024 at 12:40, Durumdara wrote:
> Hello!
>
> I have a script which can change the table owners to the database owner.
>
> I select the tables like this:
>
> FOR r IN SELECT tablename FROM pg_tables WHERE (schemaname = 'public')
> and (tableowner <> act_dbowner)
> LOOP
> ...
On Wednesday, May 1, 2024, RAJAMOHAN wrote:
>
> Main reason being I don't want the data to be copied from the database to
> their local machines.
>
You cannot stop it being copied to their local machine, you can only make
it difficult. And really not that difficult.
Trust but verify - i.e.,
Hi
You can find all user defined types with the following query.
CREATE TYPE bug_status AS ENUM ('new', 'open', 'closed');
SELECT typname
FROM pg_catalog.pg_type
JOIN pg_catalog.pg_namespace
ON pg_namespace.oid = pg_type.typnamespace
WHERE
typtype = 'e' and nspname NOT IN ('pg_catalog',
Hello!
I have a script which can change the table owners to the database owner.
I select the tables like this:
FOR r IN SELECT tablename FROM pg_tables WHERE (schemaname = 'public')
and (tableowner <> act_dbowner)
LOOP
...
For types I found pg_type, but this contains all types.
For
On Thu, May 2, 2024 at 12:50 AM Senor Cervesa
wrote:
[snip]
> I'm not sure what would trigger "directory not empty".
The lost+found directory.
I didn't used pg_dump/restore until today and finally found my mistake
which lead to the "problem" described below.
The output "depends on" comes from the -l (l as Lima) flag, what i wanted
was the -1 (number one) flag, which stands for single transaction in
pg_restore. As -l does not execute
Hi RAJAMOHAN
There is not a direct way to restrict a table not to be allowed to be
backed up by pg_dump.
But you can use the RLS (ROW LEVEL SECURITY) policy to restrict access.
Regards
Kashif Zeeshan
Bitnine Global
On Thu, May 2, 2024 at 10:47 AM RAJAMOHAN wrote:
> Hello all,
>
> In our
17 matches
Mail list logo
