Tag Info

New answers tagged

3

I was assuming that these new records will not be visible to the current transaction, but proved wrong on testing. That's not the case in the default READ COMMITTED isolation. Changes from committed transactions become visible at the start of the next statement in a transaction. Each statement still has a snapshot, so you can't have rows appear within a ...


4

What you see is completely normal and expected. Note: Because smallserial, serial and bigserial are implemented using sequences, there may be "holes" or gaps in the sequence of values which appears in the column, even if no rows are ever deleted. A value allocated from the sequence is still "used up" even if a row containing that value is never ...


2

You have an unresolved naming conflict. You must be using an old version of Postgres without declaring it. Or you are operating with non-default configuration setting. Here you declare a variable named measurement_id: DECLARE measurement_id INTEGER; It's a folly to use ambiguous variable names to begin with. If you do it anyway, you ...



Top 50 recent answers are included