> Now that Tom has gotten the ARC->2Q changes into the 8.0.x Branch, and

>Josh has had some time to do some preliminary performance
>testing on it,
>we need to put out 8.0.2 ...
>
>Core's hope is to wrap a beta up on Friday (tomorrow), and
>baring any bugs
>found in it, do a full release next Thursday.
>
>The reason for the gap is to give a bit of extra testing time
>due to the
>ARC->2Q changes ...
>
>Is anyone sitting on anything that they feel needs/should get
>into 8.0.2?

I have three pending kerberos patches, two of which are plain bugfixes
and one which I'd argue is a bugfix around a can't-compile issue, that
I'd very much like to see in 8.0.2. The bugfixes are general (both bit
me rather badly on linux while testing before I got into the win32 part
of the testing), the compile fix is win32 specific.


http://archives.postgresql.org/pgsql...3/msg00148.php
(bugfix)
http://archives.postgresql.org/pgsql...3/msg00150.php
(compile fix)
http://archives.postgresql.org/pgsql...3/msg00181.php
(bugfix)


//Magnus

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Magnus Hagander wrote:
> > Now that Tom has gotten the ARC->2Q changes into the 8.0.x Branch, and
>
> >Josh has had some time to do some preliminary performance
> >testing on it,
> >we need to put out 8.0.2 ...
> >
> >Core's hope is to wrap a beta up on Friday (tomorrow), and
> >baring any bugs
> >found in it, do a full release next Thursday.
> >
> >The reason for the gap is to give a bit of extra testing time
> >due to the
> >ARC->2Q changes ...
> >
> >Is anyone sitting on anything that they feel needs/should get
> >into 8.0.2?
>
> I have three pending kerberos patches, two of which are plain bugfixes
> and one which I'd argue is a bugfix around a can't-compile issue, that
> I'd very much like to see in 8.0.2. The bugfixes are general (both bit
> me rather badly on linux while testing before I got into the win32 part
> of the testing), the compile fix is win32 specific.
>
>
> http://archives.postgresql.org/pgsql...3/msg00148.php
> (bugfix)
> http://archives.postgresql.org/pgsql...3/msg00150.php
> (compile fix)
> http://archives.postgresql.org/pgsql...3/msg00181.php
> (bugfix)

I have all of them in the patches queue now.

--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

"Magnus Hagander" <mha@sollentuna.net> writes:
> I have three pending kerberos patches, two of which are plain bugfixes
> and one which I'd argue is a bugfix around a can't-compile issue, that
> I'd very much like to see in 8.0.2.

Working on these. Don't you have the test backwards here?

***************
*** 436,442 ****

krb5_free_principal(pg_krb5_context, server);

! if (fcntl(sock, F_SETFL, (long) flags))
{
char sebuf[256];

--- 434,440 ----

krb5_free_principal(pg_krb5_context, server);

! if (set_noblock(sock))
{
char sebuf[256];


regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match