Couple of suggestions. You might try ChatGPT. I've had some success using
this tool to uncover improvements to the use of indexes. The other would
be to look at https://explain.depesz.com/. It's pretty self-explanatory.
You run an explain plan and paste the results into the tool and it will run
You might also consider Backup/Restore. It appears you're not concerned
with data being inserted into the source table after the backup is
complete? If so, you can then easily sync the two post restore.
On Wed, Jul 23, 2025 at 6:55 AM sivapostg...@yahoo.com <
sivapostg...@yahoo.com> wrote:
> Th
Good Morning,
We have a table - I'll call it *import_job* (which is the actual name) -
that lists jobs to be executed. Each job has one or more child components
listed in another table called *import_file*.
The child table has a foreign key column called *import_job_oid*
referencing the primary
into the partitioned table.
Dropped the original table and renamed the partitioned table.
Easy, no problems. Also no 'attach'.
Thanks.
On Fri, Jun 7, 2024 at 3:31 AM Laurenz Albe
wrote:
> On Thu, 2024-06-06 at 11:28 -0500, David Barbour wrote:
> > Been an Oracle DBA for
Hi,
New to this list and to Postgres. Been an Oracle DBA for quite a while and
we're moving from Oracle to Postgres.
I have a table that I need to transform into a hash partitioned table.
I've gone through all the steps to create a hash partitioned table, with 8
partitions such as
create table
