Hmm ... I hadn't thought of that approach, but it seems pretty
reasonable offhand ... comments?
What if they change the owner of the serial sequence independently
anyway? Then dumps will be restored incorrectlynot that it matters
perhaps...
Chris
---(end of broadcast
What if they change the owner of the serial sequence independently
anyway?
I suppose a complete solution would involve forbidding that. We don't
allow you to alter the owner of an index independently of its parent
table ...
Problem is existing dump files. Oh, hang on - this is new for 8.0.
Hmmm
There is, however, an ownership problem with restoring sequences
in 8.0.0beta. In 7.4.5, for example, pg_dump issues a SET SESSION
AUTHORIZATION command and then creates a table, so implicitly-created
sequences are restored with the correct ownership. In 8.0.0beta2,
however, pg_dump doesn't issue
However, of course the best thing is to just fix it, which I guess I'll
have a crack at...
Given that pg_dump does put out GRANT/REVOKE operations on the sequence,
it's certainly aware that the sequence exists. I suspect this is just a
fixable bug (ie, suppression of output of the sequence CREAT
AFAICT there was no discussion about this issue when the patch was
proposed and applied. But now that the point is raised I have to say
that I don't like this change. I don't think system catalogs should be
excluded from tab completion. They never were before 7.4, and I have
not seen anyone com
> > The problems is that only ~15% of the lines are inserted into
> > the database. The same script modified to insert the same data in a
> > similar table created in a MySQL database inserts 100%.
>
> Did you check the error status for the records that weren't entered?
>
> My first guess is that y
Have you recompiled PHP to link against the new postgres libraries?
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Rogers
> Sent: Thursday, 27 September 2001 1:07 AM
> To: mlw
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECT
