Tom Lane wrote:
> 2. By chance, a shared-cache-inval flush comes through while it's doing
> that, causing all non-open, non-nailed relcache entries to be discarded.
> Including, in particular, the one that is "next" according to the
> hash_seq_search's status.
I thought we have catchup interrupts
Tom Lane said:
> "Michael Brown" writes:
>> I have put in place a temporary workaround on the production system,
>> which is to insert a
>
>> // Pretend that the cache is always invalid
>> fprintf ( stderr, "*** bypassing cache ***\n" );
>> goto read_failed;
>
> I don't think this w
Tom Lane said:
> I shall go and do some further investigation, but at least it's now
> clear where to look. Thanks for the report, and for being so helpful in
> providing information!
Thank you!
I have put in place a temporary workaround on the production system, which
is to insert a
//
I wrote:
> But: the question at this point is why we've never seen such a report
> before 8.4. If this theory is correct, it's been broken for a *long*
> time. I can think of a couple of possible explanations:
> A: the problem can only manifest if this loop has work to do for
> a relcache entry
"Michael Brown" writes:
> If temporary table drops count towards this, then yes.
Yeah, they do.
> I could fairly easily change this procedure to truncate rather than drop
> the temporary table, if that would lessen the exposure to the problem.
> Would that be likely to help?
Very probably. It
"Seneca Cunningham" writes:
> -- Should succeed
> DROP TABLESPACE testspace;
> + ERROR: could not read directory "pg_tblspc/40203": Invalid argument
This is a known bug in Snow Leopard :-(. We are expecting that Apple
will fix it soon, though they failed to do so in 10.6.1.
"Michael Brown" writes:
> I have put in place a temporary workaround on the production system, which
> is to insert a
> // Pretend that the cache is always invalid
> fprintf ( stderr, "*** bypassing cache ***\n" );
> goto read_failed;
I don't think this will actually help --- i
The following bug has been logged online:
Bug reference: 5080
Logged by: Seneca Cunningham
Email address: ten...@gmail.com
PostgreSQL version: 8.4.1
Operating system: OS X 10.6.0
Description:test tablespace failure
Details:
thucydides:postgresql-8.4.1 seneca$ ./conf
Michael Brown writes:
>> ... (If you have a spare machine with the same OS and
>> the same postgres executables, maybe you could put the core file on that
>> and let me ssh in to have a look?)
[ ssh details ]
Thanks for letting me poke around. What I found out is that the
hash_seq_search loop
On Thursday 24 September 2009 23:02:15 Michael Brown wrote:
> > I think this must mean that corrupt data is being read from the relcache
> > init file. The reason a restart fixes it is probably that restart
> > forcibly removes the old init file, which is good for recovery but not
> > so good for
Annita Veneti wrote:
> Matt you are absolutely right! The msysconf is not related...
> Yesterday I did some test and have seen that the access is working fine with
> postgres as long as the SSL mode is disable, as soon as I put it enabled then
> it crashes on shutdown
>
> Go figure!!!
>
> Any
"Sergey Manakov" writes:
> alter table biz_uks
> drop column remark
> ;
> create or replace function set__biz_uks()
> returns setof biz_uks
> security definer volatile language plpgsql as $$
> declare
> res biz_uks;
> begin
> return query
> select res.*;
> end;
> $$ ;
The following bug has been logged online:
Bug reference: 5078
Logged by: Sergey Manakov
Email address: vial...@gmail.com
PostgreSQL version: 8.4.1
Operating system: Fedora Core 11
Description:returns setof functions fails after table structure
altered
Details:
Hi! I
Richard Neill writes:
> I've just upgraded from 8.4.0 to 8.4.1 because of a segfault in 8.4, and
> we've found that this is still happening repeatedly in 8.4.1.
Oh dear. I just got an off-list report that seems to point to the same
kind of thing.
> The backtrace points to line 2654 in relcache
On Thu, Sep 24, 2009 at 1:53 PM, Massimiliano Ziccardi
wrote:
>>It was built on an
>>entirely different machine than any of the core postgresql binaries in
>>the release packages.
>
> Ok. I got it :-)
>
> However, the binaries I download from the postgres site didn't work without
> the microsoft p
>It was built on an
>entirely different machine than any of the core postgresql binaries in
>the release packages.
Ok. I got it :-)
However, the binaries I download from the postgres site didn't work without
the microsoft patch indicated into that email : is this an expected
behaviour?
Thank you
On Thu, Sep 24, 2009 at 1:23 PM, Massimiliano Ziccardi
wrote:
>>That shouldn't be the problem
>
> I dont' think I've understood. What is the difference between the files
> installed by the installer and the zip archive?
>
> Thank you a lot!
Nothing - but the email you referenced was discussing a
Hi Dave,
>If I had to hazard a guess, I'd say you either installed PostgreSQL
>using the zip archive of the binaries
That's exactly what I've done!
My product installation installs postgresql and than creates a window
service through the pg_ctl command.
Without that patch, none of the postgres
On Thu, Sep 24, 2009 at 12:08 PM, Massimiliano Ziccardi
wrote:
> I'm truly sorry.
>
> A while after I sent the e-mail I found the solution.
It's no problem - happens to all of us!
> Look here :
> http://archives.postgresql.org/pgadmin-support/2009-09/msg00077.php
That shouldn't be the problem.
The following bug has been logged online:
Bug reference: 5079
Logged by: dolejsi jiri
Email address: dole...@mail.ctk.cz
PostgreSQL version: 8.4.1
Operating system: FreeBSD 5.4 or Centos 5.3
Description:postgres killed by signal 11 when executing xslt_process
function
I'm truly sorry.
A while after I sent the e-mail I found the solution.
Look here :
http://archives.postgresql.org/pgadmin-support/2009-09/msg00077.php
Thanks,
Massimiliano
On Thu, Sep 24, 2009 at 12:56 PM, Massimiliano Ziccardi <
massimiliano.zicca...@gmail.com> wrote:
> Hi all.
>
> Running ev
Hi all.
Running every postgres executable on windows 2003 gives me
The system cannot execute the specified program.
Do you know any workaround?
Thanks,
Massimiliano
22 matches
Mail list logo
