Re: Assert failure due to "drop schema pg_temp_3 cascade" for temporary tables and \d+ is not showing any info after drooping temp table schema
Michael Paquier <[email protected]> Sat, 11 Jan 2020 10:41:03 +0900
| Newsgroups | gmane.comp.db.postgresql.devel.general |
|---|---|
| Message-ID | <[email protected]> |
On Fri, Jan 10, 2020 at 05:54:21PM +0530, Mahendra Singh Thalor wrote: > Thanks for the patch. I am not getting any crash but \d is not showing > any temp table if we drop temp schema and create again temp table. That's expected. As discussed on this thread, the schema has been dropped by a superuser and there are cases where it is helpful to do so, so the relation you have created after DROP SCHEMA relies on an inconsistent session state. If you actually try to use \d with a relation name that matches the one you just created, psql would just show nothing for the namespace name. -- Michael
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl4ZJ68ACgkQnvQgOdby QH2doA/+NadHiCWGw/Knvh/wcLKfgdDv9YL4iVh1ybrXlUsNSxsWop7g8mdPXG5G S7qRi4FfnMUVtyIgvlzSJCLrXYpeoWLEagVAZgw1Dpugp+hkNTT1jBV8n3qr7HA5 TriAcB420hkyO7Zjl5A/ifuJVq+r4/UTCvzZD7IiCmdnNTSwwZJ1vArxpt8TlaP4 kX2mnwfevZ2i5wD//5oXr8Z9hx6BoXBi3CX2+TRNm5VAOFfFTWdzXEQUB6wNJYBC +Uu7ETJ5IObhFJrUz2cQcGVrQjYcDJ34IxPQk0nZmR8g90Xt8Zjudq7PZDCvyJi7 Ng3YtY+2bmRIC99OXwUAUuE7xj4JigqEKgdk2MzbwfvjpAO/FmUiamDFvH/SWLIp RPKpflia5rqL/wDBE9/yFBPjEqnxDx6wh1rr4ylYWjIH7RfGi2IEJ5lmtDM4t2zS MerQ3pleIvZ7AsUaKR215owFwqn2ZSP1bhEFoFLTAyjwQFYltfvObfbo/Rmg+BrT GziCQquQ4T1XoX8xqiJBuz+DyENlbPdEVf6+l3EgTa+9OWKog2cRUbD86xmzT4LI FXinxh9sL0A1tsma8+9ohFY+aqmR+6fdyAdyqbnNhl8CDtcrdbi7L7yHvGBuOKvV L95aR8GOOs0SfijXrMhjjMo2idS8knXQIXtuA/EwwyrvF+iZD3g= =KeK2 -----END PGP SIGNATURE-----