BUG #15575: Using RDS upgrade option from 9.6 to 10.4 Upsert will not insert records but complete successfully

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: makmarath(at)hotmail(dot)com
Subject: BUG #15575: Using RDS upgrade option from 9.6 to 10.4 Upsert will not insert records but complete successfully
Date: 2019-01-04 20:31:10
Message-ID: 15575-08e99001a3dfa56a@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 15575
Logged by: Ash Marath
Email address: makmarath(at)hotmail(dot)com
PostgreSQL version: 10.4
Operating system: RDS (on AWS)
Description:

Scenario :
1.Have 2 tables created.
* main table
* audit Table
2. Create an Update trigger on Main table => The trigger will make a new
entry in the audit table
The above structure is created in v9.6
-------------------------------
ISSUE STARTS HERE
3. Use the AWS console and upgraded your PostgreSQL to ver 10x
4. Run the upsert SQL statement (update a particular column) on Main
table.
5. BUG: The column in Main table will not be updated but a new entry in the
audit table can be observed (update trigger will execute). Execute step 4
multiple times and you will notice new entries in the Audit table but record
in the main table will not be updated.
----------------------------------------
Workaround Steps to resolve this bug:
S1: Take a backup of the existing database from v9.6, generate the script
using "pg_dump" (prefer to dump output as .sql file).
S2. Create a new instance in RDS for v10.x
S3. Restore the database from the backupfile generated by pg_dump in step
S1.
-----------------------------------------------------------------
Now run the upset statement of Step 4 and you will see postgreSQL
functioning correctly. Upsert will work and existing records will be
updated.
---------------------- End of report
----------------------------------------

Thanks
Ash Marath
makmarath(at)hotmail(dot)com

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dmitry Molotkov 2019-01-04 21:01:15 Re: BUG #15446: Crash on ALTER TABLE
Previous Message PG Bug reporting form 2019-01-04 18:48:03 BUG #15574: Upgrading postgis broke pg_dump