Re: is PG able to handle a >500 GB Database?
| От | Florent Guillaume |
|---|---|
| Тема | Re: is PG able to handle a >500 GB Database? |
| Дата | |
| Msg-id | 20010119150843.A4430@twin.efge.org обсуждение исходный текст |
| Ответ на | Re: is PG able to handle a >500 GB Database? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: is PG able to handle a >500 GB Database?
|
| Список | pgsql-general |
> Unless your application logic tries to use OIDs as row identifiers, > duplicate OIDs in user tables are not a problem. Hmmm, that means that the following, which I use, is not strictly correct : create table t1 (recordid SERIAL PRIMARY KEY, val INT4, name TEXT); ... much later ... insert into t1 (val, name) values (3465, 'blah'); -- PHP application gets $lastoid for this insert select recordid from t1 where oid = $lastoid; -- PHP application now hast the recordid that was created. Because the last select could return several lines. What would be the correct idiom ? Explicitly use nextval ? That pretty defeats the point of SERIAL, no ? Florent
В списке pgsql-general по дате отправления: