RE: Problemas con pgdump

Saludos

Ante todo, debo decir que me adelanté y afirmé que las secuencias estaban
mal escritas. (disculpas por el error)

Pues no, los nombres están correctos, ya que consultando "relname" en la
tabla "pg_class" aparecen así.

Lo que no entiendo es porqué da error, si los nombres están bien, entonces
qué falla?

Os detallo por ejemplo, todas las ocurrencias de la tabla "suggeriments" y
sus objetos asociados que aparecen en el pg_dumpall:

--
-- Name: suggeriments; Type: TABLE; Schema: public; Owner: postgres;
Tablespace:
--

CREATE TABLE suggeriments (
idsuggeriment serial NOT NULL,
idprofessional integer NOT NULL,
contingut text NOT NULL
);

ALTER TABLE public.suggeriments OWNER TO postgres;

--
-- Name: suggeriment_idsuggeriment_seq; Type: SEQUENCE SET; Schema: public;
Owner: postgres
--

SELECT pg_catalog.setval(pg_catalog.pg_get_serial_sequence('suggeriments',
'idsuggeriment'), 11, true);

--
-- Data for Name: suggeriments; Type: TABLE DATA; Schema: public; Owner:
postgres
--

COPY suggeriments (idsuggeriment, idprofessional, contingut) FROM stdin;
\.

--
-- Name: suggeriment_pkey; Type: CONSTRAINT; Schema: public; Owner:
postgres; Tablespace:
--

ALTER TABLE ONLY suggeriments
ADD CONSTRAINT suggeriment_pkey PRIMARY KEY (idsuggeriment);

ALTER INDEX public.suggeriment_pkey OWNER TO postgres;

--
-- Name: suggeriments_professionals_fkey; Type: FK CONSTRAINT; Schema:
public; Owner: postgres
--

ALTER TABLE ONLY suggeriments
ADD CONSTRAINT suggeriments_professionals_fkey FOREIGN KEY
(idprofessional) REFERENCES professionals(idprofessional) ON UPDATE CASCADE
ON DELETE RESTRICT;

--
-- Name: suggeriments; Type: ACL; Schema: public; Owner: postgres
--

REVOKE ALL ON TABLE suggeriments FROM PUBLIC;
REVOKE ALL ON TABLE suggeriments FROM postgres;
GRANT ALL ON TABLE suggeriments TO postgres;
GRANT ALL ON TABLE suggeriments TO web;

--
-- Name: suggeriment_idsuggeriment_seq; Type: ACL; Schema: public; Owner:
postgres
--

REVOKE ALL ON TABLE suggeriment_idsuggeriment_seq FROM PUBLIC;
REVOKE ALL ON TABLE suggeriment_idsuggeriment_seq FROM postgres;
GRANT ALL ON TABLE suggeriment_idsuggeriment_seq TO postgres;
GRANT ALL ON TABLE suggeriment_idsuggeriment_seq TO web;

***** EL ERROR QUE APARECE AL RESTAURAR ES ********

ERROR: relation "suggeriment_idsuggeriment_seq" does not exist
ERROR: relation "suggeriment_idsuggeriment_seq" does not exist
ERROR: relation "suggeriment_idsuggeriment_seq" does not exist
ERROR: relation "suggeriment_idsuggeriment_seq" does not exist

> -----Mensaje original-----
> De: pgsql-es-ayuda-owner(at)postgresql(dot)org
> [mailto:pgsql-es-ayuda-owner(at)postgresql(dot)org] En nombre de
> Alvaro Herrera
> Enviado el: jueves, 22 de diciembre de 2005 13:24
> Para: Xavier Vidal
> CC: 'pgsql-es-ayuda:postgresql.org'
> Asunto: Re: [pgsql-es-ayuda] Problemas con pgdump
>
> Xavier Vidal escribió:
>
> > REVOKE ALL ON TABLE suggeriment_idsuggeriment_seq FROM
> PUBLIC; REVOKE
> > ALL ON TABLE suggeriment_idsuggeriment_seq FROM postgres;
> GRANT ALL ON
> > TABLE suggeriment_idsuggeriment_seq TO postgres; GRANT ALL ON TABLE
> > suggeriment_idsuggeriment_seq TO web;
>
> [falta una s]
>
> Hmm, muy raro. Haz esto:
>
> select relname from pg_class where relname like 'sugger%' and
> relkind = 's'; set enable_indexscan to off; select relname
> from pg_class where relname like 'sugger%' and relkind = 's';
>
> > REVOKE ALL ON TABLE "llibre-apartats_idapartat_seq" FROM PUBLIC;
> > REVOKE ALL ON TABLE "llibre-apartats_idapartat_seq" FROM postgres;
> > GRANT ALL ON TABLE "llibre-apartats_idapartat_seq" TO
> postgres; GRANT
> > ALL ON TABLE "llibre-apartats_idapartat_seq" TO web;
>
> [un _ fue cambiado a -]
>
> select relname from pg_class where relname like 'llibre%' and
> relkind = 's'; set enable_indexscan to off; select relname
> from pg_class where relname like 'llibre%' and relkind = 's';
>
> Cada cuanto tiempo haces vacuum de pg_class?
>
> --
> Alvaro Herrera
> http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>
> ---------------------------(fin del
> mensaje)---------------------------
> TIP 9: el optimizador ignorará el uso de recorridos de índice si los
> tipos de datos de las columnas no coinciden
>