Re: [GENERAL] import .sql file into PostgreSQL database
Just going thru old emails and came across this one. Thought to text you. How have you been? What are you up to? How can I rejoin this group? Gaurav On Wed, Apr 9, 2014 at 7:32 PM Michael Paquier wrote: > On Thu, Apr 10, 2014 at 1:02 AM, Raymond O'Donnell wrote: > > I think that message is coming from the OS; messages from Postgres are > > usual more specific, for example, "Permission denied for relation". > > > > It looks as if you haven't the OS permissions to read the SQL file. > On Windows, you need either to play with icacls to set some read > permissions or you can change it directly using the properties menu > findable by right-clicking on the culprit file. > -- > Michael >
Help regarding Multi Tenancy with PostgreSQL
Hi All, We are planing to implement multitenancy solution to store client's data seperately. We uses Django Rest Framework as backend with Postgresql version 12.11 . Is Single database multiple schemas a good solution? Is this solution works fine with django migrations? OR there can be much better solution available, Please share a resource from where I can find a proper solution. Thanks and Best Regards, Gaurav Daunde
Introduction of a new field in pg_class indicating presence of a large object in a table
Hi All, I hope you're all doing well! Recently, I have across a scenario where one of our client was unable to perform a major version upgrade of their PostgreSQL instance as it was failing due to OOM errors. When reviewed the upgrade log files and queried pg_largeobject_metadata, we found a significant number of large objects (more than a million) due to which the upgrade seems to fail. As the client had a different vendor in the past, they are unsure of why large objects were created in the first place. However, in order to further dive deep, the requirement is to identify the tables (and the columns) which contain these large objects to decide on the next steps. I checked for online resources but could not find any information that helps in this regard. Although quite different from the above specified use case, pg_class does contain a field: 'reltoastrelid' that helps us to identify the presence of a toast table for any relation in PostgreSQL. I wanted to know if there is any such system table that we can use to identify and map the fields containing large objects and the respective tables and if it is not already there, do we have any plans to incorporate the same in pg_class like we have for pg_toast? Thanks and Regards, Gaurav Pant
Postgresql support for Windows Server 2025
Greetings, Can you please let me know when Postgresql 17.x shall be supported for Windows Server 2025? Greatly appreciated your feedback. Thanks Gaurav