On Apr 1, 2012, at 13:14, Jay Levitt wrote:
> The Mac installation docs currently recommend the EDB one-click installer as
> the first choice. While this does install pgadmin and some other refinements,
> it also is fairly confusing to troubleshoot:
>
The items are not numbered and it is impo
On Apr 1, 2012, at 21:50, Jay Levitt wrote:
> Tom Lane wrote:
>> While you might not like the EDB installer, at least those
>> folks are active in the lists and accountable for whatever problems
>> their code has. Who in heck is responsible for the "homebrew"
>> packaging, and do they answer que
Tom Lane wrote:
While you might not like the EDB installer, at least those
folks are active in the lists and accountable for whatever problems
their code has. Who in heck is responsible for the "homebrew"
packaging, and do they answer questions in the PG lists?
Just for general knowledge... Wh
Dave Page wrote:
> It seems to me that most of your arguments against the installers are
> based on incorrect understanding or information, and most of your
> arguments for Homebrew actually come across as arguments against!
You're right about the former - and as to the latter, they *were* argume
Anyone else want event scheduling / cron / temporal triggers in
postgresql? http://dev.mysql.com/doc/refman/5.1/en/events-overview.html
shows how it works in mysql.
Can we throw money at someone to get this in postgres? Is there work
already being done on this?
Being able to regularly execute a p
Marko Kreen writes:
> Seems we both lost sight of actual usage scenario for the early-exit
> logic - that both callback and upper-level code *must* cooperate
> for it to be useful. Instead, we designed API for non-cooperating case,
> which is wrong.
Exactly. So you need an extra result state, o
On Sun, Apr 01, 2012 at 05:51:19PM -0400, Tom Lane wrote:
> I've been thinking some more about the early-termination cases (where
> the row processor returns zero or longjmps), and I believe I have got
> proposals that smooth off most of the rough edges there.
>
> First off, returning zero is real
On Sun, Apr 1, 2012 at 4:05 AM, Robert Haas wrote:
> My guess based on previous testing is
> that what's happening here is (1) we examine a tuple on an old page
> and decide we must look up its XID, (2) the relevant CLOG page isn't
> in cache so we decide to read it, but (3) the page we decide to
Some of my PostgreSQL Experts colleagues have been complaining to me
that servers under load with very large queries cause CSV log files that
are corrupted, because lines are apparently multiplexed. The log
chunking protocol between the errlog routines and the syslogger is
supposed to prevent t
On Sun, Apr 1, 2012 at 10:27 PM, Simon Riggs wrote:
> So lock starvation on the control lock would cause a long wait after
> each I/O, making it look like an I/O problem.
Except that both of the locks involved in his smoking gun occur
*after* the control lock has already been acquired. The one th
On Sun, Apr 1, 2012 at 1:34 PM, Robert Haas wrote:
> On Sun, Apr 1, 2012 at 7:07 AM, Simon Riggs wrote:
>> First, we need to determine that it is the clog where this is happening.
>
> I can confirm that based on the LWLockIds. There were 32 of them
> beginning at lock id 81, and a gdb session co
I've been thinking some more about the early-termination cases (where
the row processor returns zero or longjmps), and I believe I have got
proposals that smooth off most of the rough edges there.
First off, returning zero is really pretty unsafe as it stands, because
it only works more-or-less-sa
Hi
On Sun, Apr 1, 2012 at 4:14 PM, Jay Levitt wrote:
> The Mac installation docs currently recommend the EDB one-click installer as
> the first choice. While this does install pgadmin and some other
> refinements, it also is fairly confusing to troubleshoot:
>
> - By default, it installs to /Libr
Jay Levitt writes:
> So with all respect and thanks to EDB for maintaining those installers, I'd
> like to propose that homebrew become the recommended install method on Mac,
> and I will update the Mac formula to overcome any current objections.
This proposal doesn't seem to me to have any cha
Jay Levitt wrote:
POSSIBLE OBJECTIONS/PREREQUISITES
10. There is no homebrew support for multiple versions, and no current plans
to add it (though it's on the wishlist). This means homebrew is only useful
if "I want to install a PostgreSQL thingie" is the common Mac use case. If
people often
The Mac installation docs currently recommend the EDB one-click installer as
the first choice. While this does install pgadmin and some other
refinements, it also is fairly confusing to troubleshoot:
- By default, it installs to /Library/PostgreSQL, which is also (I think)
where the Apple-supp
Currently, only regular backends set the stack base pointer, for the
check_stack_depth() mechanism, in PostgresMain. We don't have stack
overrun protection in auxiliary processes. However, autovacuum workers
at least can run arbitrary user code, and if that overruns the stack,
you get a segfaul
On Sun, Apr 1, 2012 at 7:07 AM, Simon Riggs wrote:
> First, we need to determine that it is the clog where this is happening.
I can confirm that based on the LWLockIds. There were 32 of them
beginning at lock id 81, and a gdb session confirms that
ClogCtlData->shared->buffer_locks[0..31] point t
Robert Haas writes:
> How about calling it "command tag"? I think both context and toplevel
> are inconsistent with other uses of those terms: context is an
> error-reporting field, among other things; and we don't care about the
> toplevel command, just the command-tag of the one we're executing
On Sun, Apr 1, 2012 at 4:05 AM, Robert Haas wrote:
> If I filter for waits greater than 8s, a somewhat different picture emerges:
>
> 2 waited at indexam.c:521 blocked by bufmgr.c:2475
> 212 waited at slru.c:310 blocked by slru.c:526
>
> In other words, some of the waits for SLRU pages to
20 matches
Mail list logo
