As mentioned, if you are performing an INSERT/UPDATE or DELETE query and want to know the # of rows affected, you should use pg_affected_rows() instead of pg_num_rows().However, you can also exploit postgres's RETURNING clause in your query to auto-select columns from the affected rows. This has the advantage of being able to tell not only how many rows a query affects, but exactly which rows those were, especially if you return a primary-key column.For example:<?php// Example query. Let's say that this updates five rows in the source table.$res = pg_query("Update foo set bar = 'new data' where foo.bar = 'old data' ");pg_num_rows($res); // 0pg_affected_rows($res); // 5pg_fetch_all($res); // FALSE// Same query, with a RETURNING clause.$res = pg_query("Update foo set bar = 'new data' where foo.bar = 'old data' RETURNING foo.pkey");pg_num_rows($res); // 5pg_affected_rows($res); // 5pg_fetch_all($res); // Multidimensional array corresponding to our affected rows & returned columns?>