"Oeschey, Lars (I/EK-142, extern)" <extern.Lars.Oeschey@AUDI.DE> writes: > I have a table with 46 million rows, when I execute the following statement on it, I get an error: > ALTER TABLE ONLY etefas.tbl_ecu ADD CONSTRAINT pk_tbl_ecu PRIMARY KEY (pk_ecu); > HINWEIS: ALTER TABLE / ADD PRIMARY KEY erstellt implizit einen Index »pk_tbl_ecu« für Tabelle »tbl_ecu« > FEHLER: Speicher aufgebraucht > DETAIL: Fehler bei Anfrage mit GröÃe 268435456. > The statement came not from my head, but from a dump of the database (hence, the restore fails there, too). Am I doing something wrong? What have you got maintenance_work_mem set to? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match