Yeah - I reckon that would do it ;)
And it did break just about every website on our systems! Though the
change is understandable
Alex
On Thu, Feb 21, 2008 at 8:15 PM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, 21 Feb 2008 19:49:29
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 21 Feb 2008 19:49:29 -0500
"Alex Turner" <[EMAIL PROTECTED]> wrote:
> Yeah - I pressed tab to indent my code, and of course it tabbed to the
> next element on the page, which was the send button, then I hit a key,
> and it sent the message bef
Yeah - I pressed tab to indent my code, and of course it tabbed to the
next element on the page, which was the send button, then I hit a key,
and it sent the message before I was ready. I tested my hypothesis,
but it was wrong. I haven't quite figured it out yet. Something to
do with casting a c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 21 Feb 2008 17:53:35 -0500
"Alex Turner" <[EMAIL PROTECTED]> wrote:
> Upgrading to Postgres 8.3 broke virtually every site we host, and I
> finally figured out why. In 8.2 you could do this:
>
> create table foo (
No that would fail.
Did y
Upgrading to Postgres 8.3 broke virtually every site we host, and I
finally figured out why. In 8.2 you could do this:
create table foo (
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
