Hi all,
just a small note to anyone who is interested in the status of this port.
Firstly, the fork/exec changes are coming along well. The first patch, for
fork/exec'ing of backends has been accepted and applied. A second patch, for
fork/exec'ing of the remainder of the postgres process has jus
I have updated the 7.4.1 release notes so it has all the current changes
listed. We have addressed all open 7.4.1 items so we are nearing 7.4.1
release time.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Oh, okay. I would not object to suppressing pg_temp_NNN schemas from
> >> the \dn display. That isn't what this patch does, however.
>
> > OK. I read the TODO and it says only:
> > * Have psql \dn show only
[EMAIL PROTECTED] (Tom Lane) wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> Speaking of fund raising, SourceForge has just started a 'donations'
>> system whereby people can donate money to projects. Maybe you want to
>> enable it on the PostgreSQL project.
>
> Uh ... there is n
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Speaking of fund raising, SourceForge has just started a 'donations'
> system whereby people can donate money to projects. Maybe you want to
> enable it on the PostgreSQL project.
Uh ... there is no PostgreSQL project on SourceForge, AFAIK.
On Sun, 21 Dec 2003, Christopher Kings-Lynne wrote:
>
> >>Alternately, maybe it's time to try to get the fundraising operation into
> >>gear. Greg? What's our status for setup?
> >
> >
> > My goal is to have everything done by January 31st.
>
> Speaking of fund raising, SourceForge has just star
Alternately, maybe it's time to try to get the fundraising operation into
gear. Greg? What's our status for setup?
My goal is to have everything done by January 31st.
Speaking of fund raising, SourceForge has just started a 'donations'
system whereby people can donate money to projects. Mayb
Tom Lane <[EMAIL PROTECTED]> writes:
> Dmitry Tkach <[EMAIL PROTECTED]> writes:
>> This is because there are *lots* (a few million) of matches for x=10,
>> and _bt_first () scans through them *all* sequentually to get to the
>> last one.
> It's not a bug, but I agree that _bt_first can be ineffi
Shachar Shemesh <[EMAIL PROTECTED]> writes:
> Do I understand from what you are saying that we are pretty close to
> being able to perform write operations on cursors?
No, I didn't say that.
regards, tom lane
---(end of broadcast)-
Tom Lane wrote:
Rod Taylor <[EMAIL PROTECTED]> writes:
On Thu, 2003-12-18 at 10:20, Tom Lane wrote:
Is there any good reason for this restriction?
The help implies you can.
DECLARE name [ BINARY ] [ INSENSITIVE ] [ [ NO ] SCROLL ]
CURSOR [ { WITH | WITHOUT } HOLD ] FOR
Two suggestions..
1. Patch linux kernel for HT aware scheduler.
2. Try running Xeons in HTdisabled modes.
See if that helps. I would say using 2.6 on it is recommended anyways.. If
possible of course..
I would avoid 2.6 on a production machine. 2.6 breaks alot (not as in a
bad thing
Bruce Momjian wrote:
> I thought he was more concerned about removing envirnment variables
> that have to be tuned for each user. Let's see how he responds.
Think about a web server talking to a database server. Where do you set
the environment variables for that? Or where is the "home directo
12 matches
Mail list logo