On Wed, 2011-10-12 at 02:08 +0200, hans wulf wrote:
> I was wondering if the index-only-scan will be available in 9.2? This
> is not having to visit the real data to answer a query, if all the
> information is available in the index. I think this will be a mayor
> step in overtaking the big O in th
I was wondering if the index-only-scan will be available in 9.2? This is not
having to visit the real data to answer a query, if all the information is
available in the index. I think this will be a mayor step in overtaking the big
O in the g-spot.
There seams to already be some patch for this
On Thu, Oct 13, 2011 at 16:05, Tom Lane wrote:
>
> Applied with some further hacking of my own to clean up memory leaks
> and grotty coding.
Thanks!
BTW after seeing it I agree passing in fcinfo (and the other fixes) to
plperl_sv_to_datum() is better.
--
Sent via pgsql-hackers mailing list (pg
I assume this was addressed with this commit:
commit 465883b0a2b4236ba6b31b648a9eabef3b7cdddb
Author: Simon Riggs
Date: Tue Jun 28 22:58:17 2011 +0100
Introduce compact WAL record for the common case of commit
(non-DDL).
XLOG_XACT_COMMI
Heikki Linnakangas wrote:
> On 06.06.2011 16:58, Robert Haas wrote:
> > On Sun, Jun 5, 2011 at 11:26 AM, Cyan Ogilvie
> > wrote:
> >> This is my first patch, so I hope I've got the process right for submitting
> >> patches.
> >
> > You're doing great. I suspect we do want to either (1) reword wh
Should this be marked as TODO?
---
Mitsuru IWASAKI wrote:
> Hi,
>
> > On 05/07/2011 03:32 AM, Mitsuru IWASAKI wrote:
> > > For 1, I've just finish my work. The latest patch is available at:
> > > http://people.freebsd.org/
Josh Berkus wrote:
> On 6/3/11 11:01 AM, Bruce Momjian wrote:
> > According to our documentation, 'userlocks' were removed in PG 8.2:
> >
> >
> > http://developer.postgresql.org/pgdocs/postgres/runtime-config-developer.html
>
> I take it this doesn't trace advisory locks, and trace_locks doe
Josh Berkus writes:
> On 10/13/11 6:32 AM, Thom Brown wrote:
>> Could we somehow categorise these, and also do something to clarify
>> that SPI is a collection of extensions rather than an extension
>> itself?
> Alternately we should clean up SPI and break it out into its separate
> extensions.
Alex Hunsaker writes:
> This gets rid of of most of the if/else chain and the has_retval crap
> in plperl_handl_func(). Instead we let plperl_sv_to_datum() do most of
> the lifting. It also now handles VOIDOID and checks that the request
> result oid can be converted from the perl structure. For e
On Oct 13, 2011, at 9:02 PM, Tom Lane wrote:
> Alex Hunsaker writes:
>> On Wed, Oct 12, 2011 at 15:33, Alex Hunsaker wrote:
>>> On Wed, Oct 12, 2011 at 15:00, Tom Lane wrote:
The core of the problem seems to be that if SvROK(sv) then
the code assumes that it must be intended to conv
On 13 October 2011 19:46, Dimitri Fontaine wrote:
> Josh Berkus writes:
>> On 10/13/11 6:32 AM, Thom Brown wrote:
>>> Could we somehow categorise these, and also do something to clarify
>>> that SPI is a collection of extensions rather than an extension
>>> itself?
>>
>> Alternately we should cle
Josh Berkus writes:
> On 10/13/11 6:32 AM, Thom Brown wrote:
>> Could we somehow categorise these, and also do something to clarify
>> that SPI is a collection of extensions rather than an extension
>> itself?
>
> Alternately we should clean up SPI and break it out into its separate
> extensions.
Alvaro Herrera wrote:
> Excerpts from Tom Lane's message of mi?? may 25 16:07:55 -0400 2011:
> > Alvaro Herrera writes:
> > > Excerpts from Tom Lane's message of mar may 24 17:11:17 -0400 2011:
> > >> Right. It would also increase the cognitive load on the user to have
> > >> to remember the comm
On Oct 13, 2011, at 11:25 AM, Tom Lane wrote:
>> Certainly not in 9.2, no. Not sure about 9.1, though.
>
> Well, right now 9.1 is returning some rather random results. If we
> don't change it, someone might claim that later releases ought to be
> compatible with that ...
Okay then, works for me
"David E. Wheeler" writes:
> On Oct 13, 2011, at 11:02 AM, Tom Lane wrote:
>> I'm working through this patch now. Does anyone object to having the
>> array-to-non-array-result-type and hash-to-non-rowtype-result-type cases
>> throw errors, rather than returning the rather useless ARRAY(...) and
>
Oleg Bartunov wrote:
> I'm sorry, my plane to Nepal is waiting me :) I'll be back in the
> midst of November. In short, ts_rank is based only on frequencies of lexems
> and doesn't count distance between query lexems. Also, it supports only
> primitive queries.
Thanks. Attached doc patch applied
On Oct 13, 2011, at 11:02 AM, Tom Lane wrote:
> I'm working through this patch now. Does anyone object to having the
> array-to-non-array-result-type and hash-to-non-rowtype-result-type cases
> throw errors, rather than returning the rather useless ARRAY(...) and
> HASH(...) strings as pre-9.1 di
On 10/13/11 6:32 AM, Thom Brown wrote:
> Could we somehow categorise these, and also do something to clarify
> that SPI is a collection of extensions rather than an extension
> itself?
Alternately we should clean up SPI and break it out into its separate
extensions.
--
Josh Berkus
PostgreSQL Exp
Alex Hunsaker writes:
> On Wed, Oct 12, 2011 at 15:33, Alex Hunsaker wrote:
>> On Wed, Oct 12, 2011 at 15:00, Tom Lane wrote:
>>> The core of the problem seems to be that if SvROK(sv) then
>>> the code assumes that it must be intended to convert that to an array or
>>> composite, no matter wheth
Tom Lane wrote:
> Florian Pflug writes:
> > On Jun1, 2011, at 20:28 , Peter Eisentraut wrote:
> >> Well, initdb still succeeds if you give it an invalid locale name. It
> >> warns, but that can easily be missed if initdb is hidden behind a few
> >> other layers. If you then run pg_upgrade, you g
Bruce Momjian writes:
> We are not writing this software for you. Please submit a clear
> proposal. I am sure you have 10k customers who want this. :-|
I think I did (write this software).
https://github.com/dimitri/pg_staging
http://tapoueh.org/blog/2011/03/29-towards-pg_staging-10.html
Josh Berkus writes:
> (1) I cannot produce a single file in custom dump format which includes
> both a single database and all of the roles I need to build that database.
I would see addressing this with the proposal to have pg_dumpall able to
issue an archive of -Fc dumps, that pg_restore would
Peter Eisentraut wrote:
> On m?n, 2011-05-23 at 20:50 -0400, Aaron W. Swenson wrote:
> > According to Linux Standard Base Core Specification 3.1 [1], the exit
> > status should be '3' when the server isn't running.
> >
> > I've attached a very simple patch that resolves this cosmetic issue,
> > wh
The attached patch fixes this problem.
Unfortunately, we have no code that invokes get_object_address()
with missing_ok = true now, so please apply a couple of patches
to rework DROP statement of mine.
DROP TRIGGER no_such_trigger ON existing_table;
shall cause a relcache reference leaks, without
On Wed, Oct 12, 2011 at 10:50:13AM +0300, Peter Eisentraut wrote:
> Actually, I'm currently personally more concerned about the breakage we
> introduce in minor releases. We'd need to solve that problem before we
> can even begin to think about dealing with the major release issue.
+1 This b
I noticed a problem of get_object_address() with missing_ok = true.
When we try to solve the name of nonexistent rule/trigger/constraint on
a particular existing table, get_object_address_relobject() opens the
relation, but address.objectId = InvalidOid shall be set.
I think it should be closed i
On Oct 13, 2011, at 7:09 AM, Alex Hunsaker wrote:
> On Wed, Oct 12, 2011 at 15:33, Alex Hunsaker wrote:
>> On Wed, Oct 12, 2011 at 15:00, Tom Lane wrote:
>
>>> The core of the problem seems to be that if SvROK(sv) then
>>> the code assumes that it must be intended to convert that to an array
On Mon, Oct 10, 2011 at 3:56 AM, Simon Riggs wrote:
> 2011/10/9 Jun Ishiduka :
>
>> Insert WAL including a value of current FPW (on master)
>> * In the the same timing as update, they insert WAL (is named
>> XLOG_FPW_CHANGE). XLOG_FPW_CHANGE has a value of the changed FPW.
>> * When it cr
I've been thinking about the terminology used for various tools and
extensions in PostgreSQL. The documentation bundles all them together
in "Additional Supplied Modules, but really some are tools, some are
libraries and some are extensions:
Tools:
oid2name
pg_archivecleanup
pgbench
pg_standby
pg
On Tue, Oct 4, 2011 at 9:15 AM, Simon Riggs wrote:
>> Simon, could you? If your proposal turns out to be better than mine, I'd be
>> happy to agree to drop my patch and adopt yours.
>
> Yes, will do.
Simon,
I believe that we are still waiting for this.
Thanks,
--
Robert Haas
EnterpriseDB: htt
I'm sorry, my plane to Nepal is waiting me :) I'll be back in the
midst of November. In short, ts_rank is based only on frequencies of lexems
and doesn't count distance between query lexems. Also, it supports only
primitive queries.
Oleg
On Wed, 12 Oct 2011, Bruce Momjian wrote:
Bruce Momjian w
Robert,
I agree with it is a reasonable argument that compiler cannot raise warnings
if all the arguments are delivered as Datum. In fact, I also tried to implement
this feature with InvokeObjectAccessHook() defined as function.
The first needed point to be improved is that we hope compiler to ra
>
> > > > ERROR: full_page_writes on master is set invalid at least once since
> > > > latest checkpoint
> > > >
> > > > I think this error should be rewritten as
> > > > ERROR: full_page_writes on master has been off at some point since
> > > > latest checkpoint
> > > >
> > > > We should be usin
On Wed, Oct 12, 2011 at 02:27:51PM -0400, Phil Sorber wrote:
> My proposal would be to table the discussion about the 'ALTER DATABASE
> SET ROLE' case because there seems to be a bit of a philosophical
> debate behind this that needs to be sorted out first.
Note: "to table the discussion" means op
34 matches
Mail list logo
