Tuples are not inserted sequentially in database table?

Question

I am trying to insert 10 values of the format \"typename_\" + i where i is the counter of the loop in a table named roomtype with attributes typename

Answer 1

You are not seeing the order in which PostgreSQL stores the data, but rather the order in which pgadmin displays it.

The edit table feature of pgadmin automatically sorts the data by the primary key by default. that is what you are seeing.

In general, databases store table data in whatever order is convenient. Since you did not intentionally supply an ORDER BY you have no right to care what order it is actually in.

Answer 2

i guess, that the output is ordered via alphabet ... if you create typename_1 thru typename_9, everything should be ok. you can also use typename_01 ( filled up with zeros ) to get the correct order.

if you are unsure about that, you can also add a sleep between the insert statements and record the insert-time in the database( as a column )

Answer 3

This is a misunderstanding. There is no "natural" order in a relational database table. While rows are normally inserted in sequence to the physical file holding a table, a wide range of activities can reshuffle physical order. And queries doing anything more than a basic (non-parallelized) sequential scan may return rows in any opportune order. That's according to standard SQL.

The order you see is arbitrary unless you add ORDER BY to the query.

pgAdmin3 by default orders rows by the primary key (unless specified otherwise). Your column is of type varchar and rows are ordered alphabetically (according to your current locale). All by design, all as it should be.

To sort rows like you seem to be expecting, you could pad some '0' in your text:

...
typename_0009
typename_0010
...

The proper solution would be to have a numeric column with just the number, though.

You may be interested in natural-sort. You may also be interested in a serial column.