On Tuesday, March 17, 2015, Воронин Дмитрий
wrote:
> > Make sure to show your full command(s) and the full, exact text of any
> errors.
>
> OK, I use PostgreSQL version 9.4.1.
>
> I create cluster 'main' and connect to it. After cluster init we have
> those shemas:
>
> postgres=# SELECT nspname
> Make sure to show your full command(s) and the full, exact text of any
> errors.
OK, I use PostgreSQL version 9.4.1.
I create cluster 'main' and connect to it. After cluster init we have those
shemas:
postgres=# SELECT nspname FROM pg_namespace ;
nspname
p
Hello, all.
We can create temp namespaces and temp objects that contains it. So, for
example, temp table will be create at pg_temp_N (N - backendID). But afrer
cluster init we have pg_temp_1 and pg_toast_temp_1 namespaces with OIDs 11333
and 11334. Those namespaces are visible from any cluster
On 16 March 2015 at 16:31, Dmitry Voronin wrote:
> Hello, all.
>
> We can create temp namespaces and temp objects that contains it. So, for
> example, temp table will be create at pg_temp_N (N - backendID). But afrer
> cluster init we have pg_temp_1 and pg_toast_temp_1 namespaces with OIDs
> 1133
Hello, all.
We can create temp namespaces and temp objects that contains it. So, for
example, temp table will be create at pg_temp_N (N - backendID). But afrer
cluster init we have pg_temp_1 and pg_toast_temp_1 namespaces with OIDs 11333
and 11334. Those namespaces are visible from any cluster
Hello, all.We can create temp namespaces and temp objects that contains it. So, for example, temp table will be create at pg_temp_N (N - backendID). But afrer cluster init we have pg_temp_1 and pg_toast_temp_1 namespaces with OIDs 11333 and 11334. Those namespaces are visible from any cluster datab
