>> A small irritation point is that some tools decide that partitions >> under a table are to be shown in a list of tables, sometimes drowning the main table in a sea of partitions. > >While this doesn't answer your question directly, but when I had this problem, I simply moved partitions to separate schema. >So, let's say I have table plans in schema public. All its partitions are in "plans" schema. >Of course naming can be done differently, but the thing is that you can do it, and it doesn't cause any issues with queries - as long as you use main table and not directly partitions. > >Best regards, > >depesz > I had not thought of that. Nice trick. I think we have a standard security setup that revolves around schemas, that may suffer more than this helps. I will think about that some more. Thank you for the tip. Regards Niels
