Andrus,
>
> -- add bad data
> INSERT INTO foo VALUES ('');
> INSERT INTO foo VALUES ('02.x');
> INSERT INTO foo VALUES ('02.1970');
> INSERT INTO foo VALUES ('02.2101');
> INSERT INTO foo VALUES (NULL);
> -- add good data
> INSERT INTO foo VALUES ('12.2009');
>
> delete from foo where tmkuu is n
Hi Andrus,
>
> How to add column validation to table column which forces this ?
You're looking for a constraint - I presume you know what conditions you want
to check for - I've done a similar thing recently ensuring the first character
in a column is a decimal point, or that if one column's
> We just upgraded a customer's PostgreSQL installation from 8.3 to 8.4.1. I
> wanted to make a small change to the database. I wanted to take a backup
> before I did it, just in case. When I run pgAdmin from the
> PostgreSQL/8.4/bin folder and try to take a backup, the backup fails. The
>
Hi,
>
> So the issue seems to be with the last line on IPv6, to be honest i dont
> even know what IPv6 is, could disabling IPv6 do the trick or do i need to
> add something?
Your machine is connecting to PostgreSQL using IPv6's "localhost" address.
IPv6 is a newer format of IP addressing that