On Fri, Mar 26, 2010 at 12:07 PM, Robert Haas wrote:
> Hmm. I'm not sure exactly what problem you're trying to solve here.
> I don't think this is a particularly good design for supporting
> variables inside the server, since, well, it doesn't actually support
> variables inside the server. If
Robert Haas writes:
> On Sun, Jul 19, 2009 at 10:56 PM, Tom Lane wrote:
>> Yeah. Ideally this sort of thing would happen in prepjointree.c, but
>> we don't have nearly enough information at that stage.
> You've mentioned this point a couple of times - what is ideal about
> prepjointree?
Well,
On Sun, Jul 19, 2009 at 10:56 PM, Tom Lane wrote:
> Yeah. Ideally this sort of thing would happen in prepjointree.c, but
> we don't have nearly enough information at that stage.
Tom,
You've mentioned this point a couple of times - what is ideal about
prepjointree? Reading through the "optimize
Markus Wanner wrote:
Thanks,
I can now fetch off the postgres-dtester repository, but I'm still
getting the error when I try to clone the /dtester repository.
Steve,
Oh, thank you for pointing this out. I've fixed that for now.
Do I need to run git update-server-info after every pull for
Hi,
Since we insert a new entry into the index for every update that's being
made into the table, we inevitably make a unique check against the older
version of the newly inserted row, even when the values are not updated. Of
course i am talking about non-HOT updates. (We will not go to the inde
Simon Riggs writes:
> On Sun, 2010-01-31 at 23:43 +0200, Heikki Linnakangas wrote:
>> When replaying the deletion record, the standby could look at all the
>> heap tuples whose index pointers are being removed, to see which one
>> was newest.
> Long after coding this, I now realise this really is
On Sun, 2010-01-31 at 23:43 +0200, Heikki Linnakangas wrote:
> When replaying the deletion record, the standby could look at all the
> heap tuples whose index pointers are being removed, to see which one
> was newest.
Long after coding this, I now realise this really is a dumb-ass idea.
There is
Greg Stark writes:
> The Linux kernel had a big push to reduce latency, and one of the
> tricks they did was they replaced the usual interrupt points with a
> call which noted how long it had been since the last interrupt point.
> It occurs to me we could do the same for CHECK_FOR_INTERRUPTS() by
Robert Haas writes:
> As far as I know, exclusion constraints would work with hash opclasses
> also.
Yeah, they do.
> Do you think there's an advantage to having something that is
> hash-specific a la the btree-specific stuff we already have?
Sure: it'll be more efficient because of not needing
The Linux kernel had a big push to reduce latency, and one of the
tricks they did was they replaced the usual interrupt points with a
call which noted how long it had been since the last interrupt point.
It occurs to me we could do the same for CHECK_FOR_INTERRUPTS() by
conditionally having it call
On Fri, Mar 26, 2010 at 12:57 PM, Tom Lane wrote:
> Robert Haas writes:
>> In reading through the TODO list, I noticed a few things that I think
>> are done, may be done, or may be partially done. See below.
>> Thoughts? ...Robert
>
>> Add missing operators for geometric data types
>> - this is
Greg Smith writes:
> Even if there was something to be done in kernel space, how many years
> from now would it be before it made this problem go away for the
> majority of near future 9.0 users? We've been seeing a fairly regular
> stream of "pgstat wait timeout" reports come in. The one I r
Tom Lane wrote:
Should we redesign the stats signaling logic to work around this,
or just hope we can nag kernel people into fixing it?
Even if there was something to be done in kernel space, how many years
from now would it be before it made this problem go away for the
majority of near f
Robert Haas writes:
> In reading through the TODO list, I noticed a few things that I think
> are done, may be done, or may be partially done. See below.
> Thoughts? ...Robert
> Add missing operators for geometric data types
> - this is at least partly done. not sure if it is entirely done.
I
In reading through the TODO list, I noticed a few things that I think
are done, may be done, or may be partially done. See below.
Thoughts? ...Robert
Add missing operators for geometric data types
- this is at least partly done. not sure if it is entirely done.
Add OR REPLACE to CREATE LANGUAG
On Thu, Mar 25, 2010 at 11:42 PM, Joseph Adams
wrote:
> From what I can tell, a big problem with my jails idea (as well as the
> variables Robert described) is that there really isn't a way to store
> context in the backend specifically for the end client (e.g. a PHP
> script) due to connection po
Mike Lewis writes:
> I'm using the intarray contrib module[1] gin indexes on arrays (obviously)
> with postgres 9 alpha 4. I am querying to see the existence of an element.
> When I do the query normally, it performs as I'd expect (very fast). The
> explain plan looks like what I'd expect, usin
Greetings,
I'm using the intarray contrib module[1] gin indexes on arrays (obviously)
with postgres 9 alpha 4. I am querying to see the existence of an element.
When I do the query normally, it performs as I'd expect (very fast). The
explain plan looks like what I'd expect, using the index and
On 3/26/10 5:42 AM +0200, Joseph Adams wrote:
// New libpq function
pg_set('current_user', 'bob');
$result = pg_query_params(
'SELECT answer FROM secrets WHERE user=current_user AND question=$1',
array('Birth place'));
What this really does is something like:
$result = pg_quer
On Thu, Mar 4, 2010 at 9:00 PM, Fujii Masao wrote:
>> And, when we start an archive recovery from the backup from the standby,
>> we seem to reach a safe starting point before database has actually become
>> consistent. It's because backupStartLoc is zero. Isn't this an issue?
>
> This issue seems
Fujii Masao wrote:
> At the end of the handshake for replication, a CopyOutResponse
> message might not arrive at the standby for a while if there is
> no WAL record to send. Also walreceiver would get stuck until
> that message has arrived. This is not a big problem, but should
> be fixed.
>
> Th
Disclaimer: the following is only my view on the matter and is not meant
as representative of the project views, which are reached through
discussion and consensus. IOW, my 2¢.
Joseph Adams writes:
> Perhaps we could have some sort of LET statement that allows the
> client to pass data to the se
Hi,
At the end of the handshake for replication, a CopyOutResponse
message might not arrive at the standby for a while if there is
no WAL record to send. Also walreceiver would get stuck until
that message has arrived. This is not a big problem, but should
be fixed.
The cause is that walsender ha
Pei He wrote:
> I am trying to put the SP-Gist package, a general index framework for
> space partitioning trees , into Postgresql source code.
>
> SP-Gist was developed for postgresql 8.0. However, now it does not
> work with the new version.
>
> So, for the submitted patch, what version of post
24 matches
Mail list logo
