Re: [GENERAL] Insert result does not match record count

2013-07-22 Thread Natalie Wenz
I had just started to wonder if it was something that when you responded. I checked, and every case that I had where the numbers were wonky checked out when I subtracted 2^32. Whew! Thanks, Jeff! On Jul 22, 2013, at 11:20 AM, Jeff Janes wrote: > On Fri, Jul 19, 2013 at 3:20 PM, Nata

Re: [GENERAL] Insert result does not match record count

2013-07-22 Thread Natalie Wenz
l run a count on the records again, but it will take several hours. I'll post that information when I have it! On Jul 22, 2013, at 10:44 AM, Natalie Wenz wrote: > No triggers, no rules. It's just a very boring, vanilla table. I have had > plenty of cases where the inserts fai

Re: [GENERAL] Insert result does not match record count

2013-07-22 Thread Natalie Wenz
a sign of some kind of corruption? Not sure how worried I should be. Cheers, Natalie On Jul 19, 2013, at 6:14 PM, Tom Lane wrote: > Natalie Wenz writes: >> I am moving some data from one table to another in 9.2.4, and keep seeing >> this strange scenario: >> ... >&g

[GENERAL] Insert result does not match record count

2013-07-19 Thread Natalie Wenz
Hi all, I am moving some data from one table to another in 9.2.4, and keep seeing this strange scenario: insert into newtable select data from oldtable where proc_date >= x and proc_date < y; INSERT 0 78551642 select count(*) from newtable where proc_date >= x and proc_date < y; count -

[GENERAL] type-casting failures

2013-06-21 Thread Natalie Wenz
f it will fail the casting, or NULLIF and COALESCE to set a default value other than null. Or simply being able to return all of the rows where the type cast to integer, inet, date time, etc would fail. Could either, or both, of these things be candidates for adding to the project in the future? Thanks a lot! Natalie Wenz

[GENERAL] selecting for type cast failures

2013-03-07 Thread Natalie Wenz
Hi! I am working on updating some of our tables to use appropriate native data types; they were all defined as text when they were created years ago. What I am running into, though, is there are some records that have bad data in them, where they can't be successfully converted to int, or floa