| From: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
|---|---|
| To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: moving system catalogs to another tablespace |
| Date: | 2009-10-06 00:15:26 |
| Message-ID: | 4ACA8C1E.9060408@timbira.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jaime Casanova escreveu:
> it seems like we can't do this. At least a get this error:
>
> db=# alter table pg_largeobject set tablespace otro;
> ERROR: permission denied: "pg_largeobject" is a system catalog
>
> but pg_largeobject seems sensible to move to another table space for
> space considerations, no? are there any reasons for this?
> i guess i still could this with symlinks, no?
>
This was discussed some time ago [1]. A possible solution was proposed in [2]
(it's in pt-br but you can check the commands to accomplish your goal).
[1] http://archives.postgresql.org/pgsql-hackers/2004-06/msg00835.php
[2] http://listas.postgresql.org.br/pipermail/pgbr-geral/2009-March/014374.html
--
Euler Taveira de Oliveira
http://www.timbira.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-10-06 00:48:33 | Re: dblink memory leak |
| Previous Message | Brendan Jurd | 2009-10-05 23:50:02 | Re: [PATCH] DefaultACLs |