Re: [JDBC] is a good practice to create an index on the
От | Edoardo Ceccarelli |
---|---|
Тема | Re: [JDBC] is a good practice to create an index on the |
Дата | |
Msg-id | 408F679A.9030608@axa.it обсуждение исходный текст |
Ответ на | Re: [JDBC] is a good practice to create an index on the (Christopher Kings-Lynne <chriskl@familyhealth.com.au>) |
Ответы |
Re: [JDBC] is a good practice to create an index on the
Re: [JDBC] is a good practice to create an index on the |
Список | pgsql-performance |
do you mean that, declaring an index serial, I'd never have to deal with incrementing its primary key? good to know! anyway in this particular situation I don't need such accurate behaviour: this table is filled up with a lot of data twice per week and it's used only to answer queries. I could drop it whenever I want :) Thanks again, eddy Christopher Kings-Lynne ha scritto: >> I am going to use them as primary key of the table, so I'll surely >> need them unique :) > > > Eduoardo, I REALLY suggest you don't use them at all. You should make > a primary key like this: > > CREATE TABLE blah ( > id SERIAL PRIMARY KEY, > ... > ); > > Also note that by default, OIDs are NOT dumped by pg_dump. You will > need to add extra switches to your pg_dump backup to ensure that they > are. > > Chris > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster > > >
В списке pgsql-performance по дате отправления: