On Tue, Oct 02, 2007 at 08:42:28AM +0200, Magnus Hagander wrote:
> > > http://www.openssl.org/docs/crypto/ERR_set_mark.html
> > > says
> > > ERR_set_mark() and ERR_pop_to_mark() were added in OpenSSL 0.9.8.
> >
> > > Ooops. Back to the drawing board.
> >
> > To get the buildfarm going again, I a
Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
How about getting ShareUpdateExclusiveLock on manual analyze and plain
AccessShareLock on autovacuum-induced analyze?
Wouldn't fix the original problem because those two lock types don't
conflict; hence might as well keep the behavior
Tom Lane wrote:
In the worst case autovac could be starved out for a long time.
I don't have any immediate good idea about how to fix that, but
the worst consequences could be avoided if we disable the cancellation
ability when running an anti-wraparound vacuum. Further down the road
(*not* 8.3)
Sorry for replying to very old message. But... it seems this was not
backported to 8.1 or earlier. If so, how one could determine
max_fsm_pages is sufficient or not if he is running 8.1 or earlier?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
> Log Message:
> ---
> Fix free space map to correctly t
Who's in charge of editing this site? I just thought about adding my IRC
nick but the page is locked.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fir
Michael Meskes wrote:
Who's in charge of editing this site? I just thought about adding my IRC
nick but the page is locked.
as referenced on the frontpage:
http://developer.postgresql.org/index.php/Editing_Guidelines
Stefan
---(end of broadcast)--
Michael Meskes wrote:
Log Message:
---
ITAGAKI Takahiro <[EMAIL PROTECTED]> added thread-safe
descriptor handling
this seems to cause at least two different failures(linker errors and a
glibc doublefree reporting) in the ECPG-checks on multiple buildfarm
members.
Stefan
--
On Tue, Oct 02, 2007 at 02:21:02PM +0200, Stefan Kaltenbrunner wrote:
> as referenced on the frontpage:
>
> http://developer.postgresql.org/index.php/Editing_Guidelines
Argh! Being able to read definitely helps. Sorry for this.
Thanks Stefan.
Michael
--
Michael Meskes
Email: Michael at Fam-Mesk
On Tue, Oct 02, 2007 at 02:46:12PM +0200, Stefan Kaltenbrunner wrote:
> this seems to cause at least two different failures(linker errors and a
> glibc doublefree reporting) in the ECPG-checks on multiple buildfarm
> members.
Already working on it. Seems it doesn't work without threading. Will f
Magnus Hagander <[EMAIL PROTECTED]> writes:
>> I thought of a compromise. We can put back a check if the file exists
>> without using bio. That would cover some 99 percent of the messages coming
>> out of that
>> routine, I bet. And things would still work correct in 0.9.8.
> Here's an example
On Tue, Oct 02, 2007 at 02:46:12PM +0200, Stefan Kaltenbrunner wrote:
> this seems to cause at least two different failures(linker errors and a
> glibc doublefree reporting) in the ECPG-checks on multiple buildfarm
> members.
Fixed the threading enabled bug. Hopefully this fixes all problems. So
I wrote:
> Actually, if you wanted a low-hanging solution to that, it would
> probably be to revert this 8.2 patch:
> http://archives.postgresql.org/pgsql-committers/2006-09/msg00284.php
Uh ... never mind, that won't help at all. Reducing the lock taken for
ANALYZE could allow CREATE INDEX (Share
Tom Lane escribió:
> I wrote:
> > Actually, if you wanted a low-hanging solution to that, it would
> > probably be to revert this 8.2 patch:
> > http://archives.postgresql.org/pgsql-committers/2006-09/msg00284.php
>
> Uh ... never mind, that won't help at all. Reducing the lock taken for
> ANALYZ
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Tom Lane escribió:
>> It might be possible to solve this if we reduce the strength of the lock
>> used for ALTER TABLE. We'd have to go through all the commands
>> potentially issued by a pg_dump script and see if they could all be made
>> to run concur
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Sorry for replying to very old message. But... it seems this was not
> backported to 8.1 or earlier.
Since it involved a change in the FSM API, it didn't seem reasonable
to back-patch it.
regards, tom lane
---
> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > Sorry for replying to very old message. But... it seems this was not
> > backported to 8.1 or earlier.
>
> Since it involved a change in the FSM API, it didn't seem reasonable
> to back-patch it.
So for those versions of PostgreSQL the only way to kn
On Sunday 23 Sep 2007 11:31:11 pm Robert Treat wrote:
> PgAdminIII
> http://pgadmin.org/translation/
>
> phpPgAdmin
> http://phppgadmin.cvs.sourceforge.net/phppgadmin/webdb/TRANSLATORS?revision
>=1.13
Thank you focussing on postgres now.. will make it to these soon :-)
--
அன்புடன்,
ஆமாச்சு.
http
Hello,
I am implementing some functions involving index. It has some days I am with
the same problem: "ERROR: bogus pg_index tuple" in the moment of the
creation of an index. What this can be?
Grateful,
Pedro Belmino.
Pedro,
> I am implementing some functions involving index. It has some days I am
> with the same problem: "ERROR: bogus pg_index tuple" in the moment of the
> creation of an index. What this can be?
You're going to have to give a *lot* more information if you want a useful
response to your quest
Hi,
while rebuilding the entire project I ran across following warning:
.\src\interfaces\libpq\fe-secure.c(593): warning C4101: 'fp' :
unreferenced local variable
see attached diff for a fix.
-Hannes
*** ../pgsql-cvshead/src/interfaces/libpq/fe-secure.c Tue Oct 2 11:43:05 2007
--- src/inte
Magnus Hagander schrieb:
On Sun, Sep 30, 2007 at 11:30:35PM -0400, Andrew Dunstan wrote:
Tom Lane wrote:
This morning's ecpg patch certainly seems to have been snake-bit.
Although the Windows gcc buildfarm members seem happy, the MSVC ones
are all failing with
Linking...
Crea
Dropping -committers.
On Oct 2, 2007, at 10:37 AM, Tatsuo Ishii wrote:
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
Sorry for replying to very old message. But... it seems this was not
backported to 8.1 or earlier.
Since it involved a change in the FSM API, it didn't seem reasonable
to back-patch
Decibel! wrote:
> Hrm... what about adding output to vacuum verbose that indicates how many
> pages in a relation have free space? That would allow something like
> pgfouine to see how many FSM pages were needed. It would also make it
> easier to identify relations that could stand a vacuum ful
Decibel! <[EMAIL PROTECTED]> writes:
> Hrm... what about adding output to vacuum verbose that indicates how
> many pages in a relation have free space?
Did you forget the context here? This is 8.1 and before that we're
worried about; we're not making such changes in stable releases.
> > Since this is an actual API library, perhaps a proper fix is to create a
> > .def file listing the exports in it, the same way we do for libpq? And then
> > we could (should!) also filter the exports the same ways as we do for libpq
> > these days.
> >
> > (see the exports.txt file in libpq)
>
25 matches
Mail list logo
