While I was poking around at the index-only scans patch, I couldn't
help noticing that our buffer replacement algorithm leaves something
to be desired. Here's the query again:
select sum(aid) from sample_data a1 where exists (select * from
pgbench_accounts a where a.aid = a1.aid and a.aid != 1234
On Thu, Aug 11, 2011 at 9:44 PM, Greg Sabino Mullane wrote:
>>> Maybe it's time to finally remove the been-deprecated-for-a-while OIDs?
>
>> I thought about just not supporting that for index-only scans, but
>> system catalogs use them pretty extensively, and it doesn't seem out
>> of the question
2011/8/11 Shigeru Hanada :
> Yeah, I have (hopefully) working FDW for PostgreSQL which is based on
> the one which has been proposed for 9.1, and updates done by Heikki.
> I've implemented:
>
> * SELECT clause omitting
> * WHERE clause pushdown (assuming remote has same functions/oprators)
> * p
On Thu, Aug 11, 2011 at 5:09 PM, Tom Lane wrote:
> I can reproduce the problem fairly conveniently with this crude hack:
>
> diff --git a/src/backend/storage/ipc/sinval.c
> b/src/backend/storage/ipc/sinval.c
> index 8499615..5ad2aee 100644
> *** a/src/backend/storage/ipc/sinval.c
> --- b/src/back
On Thu, Aug 11, 2011 at 5:39 PM, Cédric Villemain
wrote:
> 2011/8/11 Robert Haas :
>> Please find attached a patch implementing a basic version of
>> index-only scans. This patch is the work of my colleague Ibrar Ahmed
>> and myself, and also incorporates some code from previous patches
>> posted
(2011/08/12 0:48), Robert Haas wrote:
> 2011/8/9 Shigeru Hanada:
>> postgres=# \d pgbench_accounts
>>Foreign table "public.pgbench_accounts"
>> Column | Type | Modifiers |Options
>> --+---+---+---
>> aid | integer | not nu
On 08/11/2011 09:44 PM, Greg Sabino Mullane wrote:
I guess the question that should be asked is "we are going to finally
remove OIDs someday, right?". If so, and if it's potentially blocking a
major new feature, why not now?
It seems a bit odd then that we added "ALTER TABLE SET WITH OIDS"
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
>> Maybe it's time to finally remove the been-deprecated-for-a-while OIDs?
> I thought about just not supporting that for index-only scans, but
> system catalogs use them pretty extensively, and it doesn't seem out
> of the question that that c
2011/8/11 Robert Haas :
> Please find attached a patch implementing a basic version of
> index-only scans. This patch is the work of my colleague Ibrar Ahmed
> and myself, and also incorporates some code from previous patches
> posted by Heikki Linnakanagas.
Great!.
>
> I'm able to demonstrate a
I wrote:
> I still haven't reproduced the behavior here, but I think I see what
> must be happening: we are getting an sinval reset while attempting to
> open pg_class_oid_index.
After a number of false starts, I've managed to reproduce this behavior
locally. The above theory turns out to be wron
On Thu, Aug 11, 2011 at 4:57 PM, Greg Sabino Mullane wrote:
>> 1. The way that nodeIndexscan.c builds up the faux heap tuple is
>> perhaps susceptible to improvement. I thought about building a
>> virtual tuple, but then what do I do with an OID column, if I have
>> one? Or maybe this should be
On 08/11/2011 01:57 PM, Greg Sabino Mullane wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
1. The way that nodeIndexscan.c builds up the faux heap tuple is
perhaps susceptible to improvement. I thought about building a
virtual tuple, but then what do I do with an OID column, if I h
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> 1. The way that nodeIndexscan.c builds up the faux heap tuple is
> perhaps susceptible to improvement. I thought about building a
> virtual tuple, but then what do I do with an OID column, if I have
> one? Or maybe this should be done some o
Simon Riggs wrote:
> On Sat, Aug 6, 2011 at 4:16 AM, Bruce Momjian wrote:
>
> > Well, if the table is created in the same transaction (which is the only
> > case under consideration), no other sessions can write to the table so
> > you are just writing the entire table on commit, rather than to t
On Thu, Aug 11, 2011 at 2:28 PM, Heikki Linnakangas <
heikki.linnakan...@enterprisedb.com> wrote:
> On 10.08.2011 22:44, Alexander Korotkov wrote:
>
>> Manual and readme updates.
>>
>
> Thanks, I'm reviewing these now.
>
> Do we want to expose the level-step and buffersize parameters to users?
> T
On Thu, 2011-08-11 at 11:58 -0400, Robert Haas wrote:
> I'm OK with adding a note either to the 9.0 docs only (which means it
> might be missed by a 9.0 user who only looks at the current docs) or
> with adding a note to all versions mentioning the difference in
> behavior with 9.0, but I'm not rea
Hannu Krosing writes:
>> Hm, you mean reverse-engineering the parameterization of the query?
>
> Yes, basically re-generate the query after (or while) parsing, replacing
> constants and arguments with another set of generated arguments and
> printing the list of these arguments at the end. It may
Robert Haas writes:
> On Tue, Aug 9, 2011 at 2:16 PM, Peter Eisentraut wrote:
>> But I'm a little confused by what this code is really trying
>> to accomplish: ...
> I think the intended behavior of NI_NUMERICHOST is to suppress the
> name lookup, and return the text format *even if* the name lo
On Thu, Aug 11, 2011 at 1:02 AM, senthilnathan
wrote:
> What is the basic reason for restricting backup at standby
> server(pg_start_backup)?
It performs a checkpoint.
> We are doing the following steps to take backup from standby which(backups)
> might be used for standalone startups.
>
> 1.Cre
Hello,
We are in the final 48 hours of the CFP for PgWest. Let's get those
talks in.
https://www.postgresqlconference.org/talk_types
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
The Pos
On Thu, Aug 11, 2011 at 12:04 PM, Alvaro Herrera
wrote:
> Excerpts from Robert Haas's message of jue ago 11 11:50:40 -0400 2011:
>> 2011/8/9 Shigeru Hanada :
>
>> >>> (3) OPTIONS clause style
>> >>> Show FDW options as they were in OPTIONS clause. Each option is shown
>> >>> as "key 'value'", and
Excerpts from Robert Haas's message of jue ago 11 11:50:40 -0400 2011:
> 2011/8/9 Shigeru Hanada :
> >>> (3) OPTIONS clause style
> >>> Show FDW options as they were in OPTIONS clause. Each option is shown
> >>> as "key 'value'", and delimited with ','.
> >>>
> >>> Ex)
> >>> FDW Options:
Hi there,
plpython crashes on me on various 64-bit Ubuntu hosts, see the gdb
backtrace at: https://gist.github.com/1140005
Do you believe there was recent bugfixes regarding PLyMapping_ToTuple() ?
This is PG 9.0.4 with HEAD of plpython taken in march 2011 and backported.
Please tell me if you n
On Sun, Jul 10, 2011 at 3:29 PM, Jeff Davis wrote:
> On Sun, 2011-07-10 at 00:36 -0400, Alvaro Herrera wrote:
>> Is this really a good idea? I think the note should still be there in
>> 9.1 and beyond (with the version applicability note of course)
>
> I see your point, but it also seems strange
2011/8/9 Shigeru Hanada :
> (2011/08/09 1:16), Robert Haas wrote:
>> 2011/8/8 Shigeru Hanada:
> Currently table-level options are showin in result of \det+ command
> (only verbose mode), in same style as fdw and foreign servers.
>
> But \d is more popular for table describing, so mo
2011/8/9 Shigeru Hanada :
> postgres=# \d pgbench_accounts
> Foreign table "public.pgbench_accounts"
> Column | Type | Modifiers | Options
> --+---+---+---
> aid | integer | not null | {colname=aid}
> bid | integer
On Mon, Aug 8, 2011 at 6:01 PM, Josh Kupershmidt wrote:
> On Mon, Aug 8, 2011 at 4:34 PM, Robert Haas wrote:
>> OK, I've now committed most of this, with some additions to the
>> documentation. Remaining bits attached.
>
> Looks good, thanks.
And now I've committed (nearly) all of what remains.
What is the basic reason for restricting backup at standby
server(pg_start_backup)?
We are doing the following steps to take backup from standby which(backups)
might be used for standalone startups.
1.Create file system snapshot(LVM)
2.take the back up of data directory including wal files
3.Drop
On 08/11/2011 10:46 AM, Tom Lane wrote:
Marko Kreen writes:
On Wed, Aug 10, 2011 at 9:19 PM, Tom Lane wrote:
... which this approach would create, because digest() isn't restricted
to just those algorithms. I think it'd be better to just invent two
new functions, which also avoids issues f
2011/8/9 Shigeru Hanada :
> I'm the author of that patch, sorry for confusion. May I explain the
> background of implementing those command? :)
>
> Basically, during implementing foreign table support, I tried to follow
> the existing design.
>
> I found two backslash command groups in psql, \de[w
Marko Kreen writes:
> On Wed, Aug 10, 2011 at 9:19 PM, Tom Lane wrote:
>> ... which this approach would create, because digest() isn't restricted
>> to just those algorithms. I think it'd be better to just invent two
>> new functions, which also avoids issues for applications that currently
>> e
On Thu, Aug 11, 2011 at 10:30 AM, Tom Lane wrote:
> Andres Freund writes:
>>> --On 10. August 2011 21:54:06 +0300 Heikki Linnakangas
>>> wrote:
So my theory is that if the I/O is really busy, write() on the stats file
blocks for more than 5 seconds, and you get the timeout.
>
>> Yes, I
Andres Freund writes:
>> --On 10. August 2011 21:54:06 +0300 Heikki Linnakangas
>> wrote:
>>> So my theory is that if the I/O is really busy, write() on the stats file
>>> blocks for more than 5 seconds, and you get the timeout.
> Yes, I have seen it several times as well. I can actually reprodu
On 08/11/2011 09:42 AM, pasman pasmański wrote:
Its problem on my computer. But prepacked souces compile good.
Maybe git need specific configuration for postgres ?
Or some buggy sed/gawk/grep skip pg_config.h file?
1.
A: Because we read from top to bottom, left to right.
Q: Why s
On Tue, Aug 9, 2011 at 2:16 PM, Peter Eisentraut wrote:
> When a host name is used in pg_hba.conf, then we call
> pg_getnameinfo_all() to get the host name for the client's IP address,
> either in postmaster.c or in hba.c, whichever happens first. But if the
> IP address has no host name, the get
On 10.08.2011 22:44, Alexander Korotkov wrote:
Manual and readme updates.
I went through these, and did some editing and rewording. Attached is an
updated README, and an updated patch of the doc changes. Let me know if
I screwed up something.
--
Heikki Linnakangas
EnterpriseDB http://
Its problem on my computer. But prepacked souces compile good.
Maybe git need specific configuration for postgres ?
Or some buggy sed/gawk/grep skip pg_config.h file?
2011/8/11, pasman pasmański :
> Hi.
>
> Compiling 9.1 sources from packed tgz file works ok.
>
> When compile sources loaded fro
On 08/11/2011 08:58 AM, pasman pasmański wrote:
Hi.
Compiling 9.1 sources from packed tgz file works ok.
When compile sources loaded from git repository,
configure pass without errors, config.log looks ok,
but in src/include/pg_config.h aren't any defines, only undefines.
It seems like src/in
On Wed, Aug 10, 2011 at 9:19 PM, Tom Lane wrote:
> Peter Eisentraut writes:
>> I would like to see whether there is support for adding sha1 and sha2
>> functions into the core.
>
> I can't get excited about that, but could put up with it as long as
> there wasn't scope creep ...
>
>> One thing th
On 10.08.2011 22:44, Alexander Korotkov wrote:
Manual and readme updates.
Thanks, I'm reviewing these now.
Do we want to expose the level-step and buffersize parameters to users?
They've been useful during testing, but I'm thinking we should be able
to guess good enough values for them autom
On Wed, Aug 10, 2011 at 11:45 PM, Heikki Linnakangas <
heikki.linnakan...@enterprisedb.com> wrote:
> unloadNodeBuffers() is now dead code.
>
processEmptyingStack calls it.
LEAF_PAGES_STATS_* are unused now.
Removed.
> Should avoid calling smgrnblocks() on every tuple, the overhead of that
> co
On Thursday, August 11, 2011 11:49:12 Bernd Helmle wrote:
> --On 10. August 2011 21:54:06 +0300 Heikki Linnakangas
>
> wrote:
> > So my theory is that if the I/O is really busy, write() on the stats
> > file
> > blocks for more than 5 seconds, and you get the timeout.
>
> I've seen it on custome
--On 10. August 2011 21:54:06 +0300 Heikki Linnakangas
wrote:
So my theory is that if the I/O is really busy, write() on the stats file
blocks for more than 5 seconds, and you get the timeout.
I've seen it on customer instances with very high INSERT peak loads (several
dozens backends IN
On Aug11, 2011, at 09:16 , Peter Eisentraut wrote:
> On fre, 2011-07-29 at 11:37 +0200, Florian Pflug wrote:
>> On Jul28, 2011, at 22:51 , Peter Eisentraut wrote:
>>> On ons, 2011-07-27 at 23:21 +0200, Florian Pflug wrote:
On Jul27, 2011, at 23:08 , Peter Eisentraut wrote:
> Well, offhand
On Thu, Aug 11, 2011 at 09:06, Peter Eisentraut wrote:
> On ons, 2011-08-10 at 14:19 -0400, Tom Lane wrote:
>> > One thing that might be reasonable would be to move the digest()
>> > functions
>> > digest(data text, type text) returns bytea
>> > digest(data bytea, type text) returns bytea
On Thu, Aug 11, 2011 at 10:21 AM, Heikki Linnakangas <
heikki.linnakan...@enterprisedb.com> wrote:
> Split of an internal node works like this:
>
> 1. Gather all the existing tuples on the page, plus the new tuple being
> inserted.
> 2. Call picksplit on the tuples, to divide them into pages
> 3.
On fre, 2011-07-29 at 11:37 +0200, Florian Pflug wrote:
> On Jul28, 2011, at 22:51 , Peter Eisentraut wrote:
> > On ons, 2011-07-27 at 23:21 +0200, Florian Pflug wrote:
> >> On Jul27, 2011, at 23:08 , Peter Eisentraut wrote:
> >>> Well, offhand I would expect that passing an XML value to XMLATTRIBU
On ons, 2011-08-10 at 14:19 -0400, Tom Lane wrote:
> > One thing that might be reasonable would be to move the digest()
> > functions
> > digest(data text, type text) returns bytea
> > digest(data bytea, type text) returns bytea
> > from pgcrypto into core,
>
> ... which this approach woul
On ons, 2011-08-10 at 18:53 -0400, Tom Lane wrote:
> Dave Byrne writes:
> > Attached is a patch that skips orphaned temporary relations in pg_upgrade
> > if they are lingering around. It works for 9.0 -> 9.1 upgrades, however I
> > wasn't able to tell when pg_class.relistemp was added so if it w
49 matches
Mail list logo
