- Thank you received: 0
metadata hot standby refresh
- tjosh52
- Topic Author
- Offline
- User
-
Less
More
5 years 8 months ago #14445
by tjosh52
metadata hot standby refresh was created by tjosh52
We currently have 2 linked servers. One connected to the main DB for writing and a hot standby that is used for reading. When the main DB has a column modified or added we can refresh the cache without issue. This replicates over to the hot standby but the driver for PGOLEDB does not see it. When we try to run the cache update it fails. We are on the latest version of the PGOLEDB driver.
OLE DB provider "PGNP" for linked server "pgsql3" returned message "Undefined column name identificationbatchid__c".
Msg 7321, Level 16, State 2, Line 1
An error occurred while preparing the query "SELECT identificationbatchid__c FROM salesforce.member_master__c;" for execution against OLE DB provider "PGNP" for linked server "pgsql3".
EXEC('pgnp_refreshmetadata('''',''enrollment_status_move_batch'')') AT pgsql2 -- works fine
EXEC('pgnp_refreshmetadata('''',''enrollment_status_move_batch'')') AT pgsql3 -- fails
OLE DB provider "PGNP" for linked server "pgsql3" returned message "ERROR: cannot execute NOTIFY during recovery
".
OLE DB provider "PGNP" for linked server "pgsql3" returned message "ERROR: cannot execute LISTEN during recovery
".
OLE DB provider "PGNP" for linked server "pgsql3" returned message "Undefined column name identificationbatchid__c".
Msg 7321, Level 16, State 2, Line 1
An error occurred while preparing the query "SELECT identificationbatchid__c FROM salesforce.member_master__c;" for execution against OLE DB provider "PGNP" for linked server "pgsql3".
EXEC('pgnp_refreshmetadata('''',''enrollment_status_move_batch'')') AT pgsql2 -- works fine
EXEC('pgnp_refreshmetadata('''',''enrollment_status_move_batch'')') AT pgsql3 -- fails
OLE DB provider "PGNP" for linked server "pgsql3" returned message "ERROR: cannot execute NOTIFY during recovery
".
OLE DB provider "PGNP" for linked server "pgsql3" returned message "ERROR: cannot execute LISTEN during recovery
".
Please Log in or Create an account to join the conversation.
- admin
- Offline
- Admin
-
Less
More
- Thank you received: 8
5 years 8 months ago #14447
by admin
Replied by admin on topic metadata hot standby refresh
The LISTEN/NOTIFY logic can be disabled, for the linked server connected to the hot standby, by adding the following parameter to the Provider String/Extended Properties: EVENTS=NONE.
In this case the PGNP provider should just reset its internal metadata cache, without sending notification to the hot standby. However, you will need build 1.4.0.3500 or later.
In this case the PGNP provider should just reset its internal metadata cache, without sending notification to the hot standby. However, you will need build 1.4.0.3500 or later.
Please Log in or Create an account to join the conversation.
Time to create page: 0.143 seconds