Search Path vs Synonyms - Mailing list pgsql-general

From Matthew Seaborn
Subject Search Path vs Synonyms
Date
Msg-id 30E6B5904E5C814BA7EF81A95FFCD1EA0117B48B4A32@PTVEXCCL01.ptv.com
Whole thread Raw
Responses Re: Search Path vs Synonyms
List pgsql-general

Given the situation where a user connecting to the database needs access to two separate schemas: the primary schema which contains the data they will be updating and a second schema which contains read-only reference data, used by many users, that will be using in joins on queries.

 

I don’t want to have to use fully qualified names (I am migrating code from Oracle which uses synonyms), so what is the best way (in both performance and reliability) to refer to the tables;  Search Path or Synonyms?

 

Thanks.

 


________________________________________________________________________

CONFIDENTIALITY - This email and any files transmitted with it, are confidential, may be legally privileged and are intended solely for the use of the individual or entity to whom they are addressed. If this has come to you in error, you must not copy, distribute, disclose or use any of the information it contains. Please notify the sender immediately and delete them from your system.

SECURITY - Please be aware that communication by email, by its very nature, is not 100% secure and by communicating with Perform Group by email you consent to us monitoring and reading any such correspondence.

VIRUSES - Although this email message has been scanned for the presence of computer viruses, the sender accepts no liability for any damage sustained as a result of a computer virus and it is the recipient�s responsibility to ensure that email is virus free.

AUTHORITY - Any views or opinions expressed in this email are solely those of the sender and do not necessarily represent those of Perform Group.

COPYRIGHT - Copyright of this email and any attachments belongs to Perform Group, Companies House Registration number 6324278.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: ERROR: unexpected data beyond EOF in block of relation "RelationName"
Next
From: Jan-Erik
Date:
Subject: split string by special characters