Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > However, I don't see any CVS commit that fixed this? What am I missing?
>
> The failure case is where the template database has a conflicting
> table. You didn't show us where you created that table, but it
> evidently was not in te
On Sat, 14 Aug 2004, Bruce Momjian wrote:
> Christopher Kings-Lynne wrote:
> > > Yeah, those are all bug fixes and okay for post-beta I think. But which
> > > two tablespace failures are you thinking of exactly? The last couple
> > > weeks have been a bit of a blur for me...
> >
> > http://group
Bruce Momjian <[EMAIL PROTECTED]> writes:
> However, I don't see any CVS commit that fixed this? What am I missing?
The failure case is where the template database has a conflicting
table. You didn't show us where you created that table, but it
evidently was not in template1.
Tom Lane wrote:
> > http://groups.google.com.au/groups?q=tablespaces+group:comp.databases.postgresql.hackers&hl=en&lr=&ie=UTF-8&group=comp.databases.postgresql.hackers&scoring=d&selm=4107211C.2050508%40familyhealth.com.au&rnum=5
>
> I think the problem here is that we don't have a syntax for sayin
Christopher Kings-Lynne wrote:
> > Yeah, those are all bug fixes and okay for post-beta I think. But which
> > two tablespace failures are you thinking of exactly? The last couple
> > weeks have been a bit of a blur for me...
>
> http://groups.google.com.au/groups?q=tablespaces+group:comp.databa
On Fri, 13 Aug 2004, Bruce Momjian wrote:
>
> Where are we on this?
>
> ---
>
> Tom Lane wrote:
> > Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> > >> Yeah, those are all bug fixes and okay for post-beta I think. But
The other tablespace problem is if you drop a tablespace that schema in
another db uses, it's broken still I think.
Chris
Bruce Momjian wrote:
Where are we on this?
---
Tom Lane wrote:
Christopher Kings-Lynne <[EMAIL PROTECTE
Where are we on this?
---
Tom Lane wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> >> Yeah, those are all bug fixes and okay for post-beta I think. But which
> >> two tablespace failures are you thinking of e
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> Yeah, those are all bug fixes and okay for post-beta I think. But which
>> two tablespace failures are you thinking of exactly? The last couple
>> weeks have been a bit of a blur for me...
> http://groups.google.com.au/groups?q=tablespaces+g
Yeah, those are all bug fixes and okay for post-beta I think. But which
two tablespace failures are you thinking of exactly? The last couple
weeks have been a bit of a blur for me...
http://groups.google.com.au/groups?q=tablespaces+group:comp.databases.postgresql.hackers&hl=en&lr=&ie=UTF-8&group=
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Tom, I haven't had a comment on the 'restoring LOB comments' patch, nor
> on the two tablespace failures that Gavin and I brought up (Or the
> original schema tablespace problem you found when you committed). They
> could probably be post-be
If anyone has time to work on docs over the next two days, please show
up on pgsql-docs and let us know what you want to work on. (And of
course it's still open season for bug-fix patches.)
Tom, I haven't had a comment on the 'restoring LOB comments' patch, nor
on the two tablespace failures that
I've fixed dbsize here and will send it off once I get a second to test it
with multiple tablespaces.
I haven't looked at oid2name.
Bruce put together some ideas a few months back on what we want from
oid2name now (somewhere around here:
http://archives.postgresql.org/pgsql-patches/2004-06/msg002
On Thu, Aug 05, 2004 at 07:58:14PM -0400, Tom Lane wrote:
> AFAIK there are no major patches still outstanding, with the
> exception of the Windows-symlinks patch that arrived today from
> Andreas. Bruce and I both think that's worth getting in, if no one
> has any objections, but otherwise we ess
AFAIK there are no major patches still outstanding, with the exception
of the Windows-symlinks patch that arrived today from Andreas. Bruce
and I both think that's worth getting in, if no one has any objections,
but otherwise we essentially have 8.0beta1 code.
The documentation, however, desperat
15 matches
Mail list logo
