Further investigation shows the logs are next to useless there is nothing in the logs at all that gives even an indication as to the cause of the problem, i am starting to think I have somehow triggered quite a nasty bug.
I currently can't schedule any shows at all if it was not for the fact that i have a back up sever (not running airtime) i would be off the air and my station would be in trouble.
I am starting to question whether airtime is actually a viable solution for professional stations.
Airtime seems to have serious problems with the calendar/scheduler. I don't know if the problem comes from Postgresql or Airtime itself.
Airtime is a very interesting project, developers havedone a remarkable job to run this product. But for the moment I think it's for personal/testing use, due to major bugs still presents.
It works quite well in general since the 2.5 version.
I am starting to think its an airtime bug, although i am struggling to find anyone who has had a similar problem.
I have been doing a bit more digging, it would seem that this problem only manifests itself if you try to add content to a show that has no end (it previously worked fine).
If for example I add a show to run for a year then the content is added without a problem.
It worked fine for the last couple of months with shows set to never end, its only developed the issue since deleting some shows to create new ones, but i do tend to agree with you may be i am asking a bit much from it :-)