Dear All,
Thank you for your emails which were very helpful.
I've finally solved it.
template1 was full of data, presumably somehow from a badly-run dump and
restore.
So when I created the new database, that too was full of data from the
template.
I ran a clean pg_dump on template1 from my p
ratch, and try again.
Thanks,
Malcolm
Vidhya Bondre ha scritto:
can you specify the exact commands and the sequence. With this set up
it should work.
how do you import the data.
Vidhya
On Wed, Nov 18, 2009 at 5:18 PM, Malcolm Warren
mailto:malc...@villeinitalia.com>> wrote:
creating the same tables in the new database?
Same sort of problem with psql:
If I run 'psql database2' then I see everything from database1 as well.
What am I missing here?
Thanks for your time.
Malcolm Warren
The answer is 3. Mistake of mine. I put in a field of the same name to
display it, and it was also sending 0 with the statement.
Thank you for helping me get to the bottom of it.
Malcolm Warren
Richard Huxton wrote:
Malcolm Warren wrote:
Thank you for your reply.
Yes, I get the next number and
I have been using a serial column in my most important postgres table
for a couple of years.
But today it has suddenly started assigning zero instead of the next
number, which clearly is causing chaos.
I have restarted Postgres, but it has not solved the problem. I cannot
re-assign the serial n
que, tells you how to use them, actually
gives an example of using them as primary and foreign keys (which
fortunately I decided was not very wise) and certainly doesn't say anything
about phasing them out in the future.
Can anybody shed any light on this?
Malcolm Warren
