On Wed, Nov 3, 2010 at 9:30 PM, Vaibhav Kaushal
wrote:
> I read a few things about development in the open source area on different
> websites, had a talk with a few friends and thought that I cannot work on
> the development branch of postgres right now.
ok
> So I have this one single question:
I read a few things about development in the open source area on different
websites, had a talk with a few friends and thought that I cannot work on
the development branch of postgres right now.
So I have this one single question:
Would I be able to get the answers if I asked questions about the
On 14/10/10 15:53, Alastair Turner wrote:
It isn't a TODO item, or related to any previous thread I could find.
It's certainly something I can see a use for. When I'm having a bad
typing day I get annoyed that I find I've made a mistake after I've
typed the password. To me this is a feature
On Wed, Nov 3, 2010 at 2:19 AM, Michael Meskes wrote:
> On Mon, Nov 01, 2010 at 12:17:02PM +0900, Itagaki Takahiro wrote:
>> There are some "== true" in the codes, but they might not be safe
>> because all non-zero values are true in C. Is it worth cleaning up them?
Here is a proposed cleanup tha
On Tue, Nov 2, 2010 at 10:38 PM, Dimitri Fontaine
wrote:
> Fujii Masao writes:
>> After 9.0 release, I've often heard that some people want to know
>> how far transactions have been replayed in the standby in timestamp
>> rather than LSN. So I'm thinking to include the function which returns
>> t
Alvaro Herrera writes:
> FWIW I think you should use getObjectDescription, as in the attached
> patch. (Note the patch is incomplete and does not compile because only
> one caller to CheckSetNamespace has been fixed).
That a very good idea, will apply (cherry-pick -n) and finish it
tomorrow, tha
Hackers,
Seg contrib module contains the same bug in picksplit function as cube
contrib module.
Also, Guttman's split algorithm is not needed in unidimensional case,
because sorting based algorithm is good in this case. I propose the patch
which replace current picksplit implementation with sortin
Excerpts from Dimitri Fontaine's message of mié nov 03 13:10:12 -0300 2010:
> Then, I think the ALTER EXTENSION foo SET SCHEMA name still has a use
> case, so I've prepared a simple patch to show the API usage before we
> get to refactor it all following Tom's asking. So there's a initial
> patch
On Nov 3, 2010, at 2:06 PM, Alex Hunsaker wrote:
>> try:
>>plpy.execute("insert into foo values(1)")
>> except plpy.UniqueViolation, e:
>>plpy.notice("Ooops, you got yourself a SQLSTATE %d", e.sqlstate)
>
> Ouuu .
>
> [ now that eval { }, thanks to Tim Bunce, works with plperl it should
On Wed, Nov 3, 2010 at 14:43, Jan Urbański wrote:
> By the way, I'm leaning in the direction of not using a Python
> dictionary for the cache, but a standard Postgres HTAB instead. It's
> more like other pls this way, and you can get rid of PyCObjects (which
> are deprecated BTW) and messing aroun
On 03/11/10 20:57, Alex Hunsaker wrote:
> On Wed, Nov 3, 2010 at 10:28, Tom Lane wrote:
>> OK, applied.
>
> Thanks!
>
>> I notice that plpython is also using the trigger relation's OID, but I
>> don't know that language well enough to tell whether it really needs to.
>
> This thread was started
Hi SQL/MED developers,
Our company has just finished development of a database extension for
Informix that provides tabular access to various types of structured
files (NetCDF and HDF5, with more types to come). We would like to
port this logic to run on PostgreSQL, since many of our potential
Andres Freund wrote:
> I guess you built both in the same place and just prefix installed
> it to different directories?
We always build in a directory tree with a name based on the
version, with a prefix based on the version. This is routine for
us. I have a hard time believing that they ma
On Wed, Nov 3, 2010 at 10:28, Tom Lane wrote:
> OK, applied.
Thanks!
> I notice that plpython is also using the trigger relation's OID, but I
> don't know that language well enough to tell whether it really needs to.
This thread was started by someone working a plpython a validator, I
figured t
Hi,
On Wednesday 03 November 2010 20:28:03 Kevin Grittner wrote:
> They said that except for the quirky path behavior, the installation
> went fine; the Wiki page instructions were clear and adequate and
> that installation process was not difficult or confusing.
>
> This path issue sounds like a
[going back on list with this]
Selena Deckelmann wrote:
> Kevin Grittner > the other three DBAs here implemented the HS/SR while I was out
>> They told me that it was working great once they figured it out,
>> but it was confusing; it took them a lot of time and a few false
>> starts to get it
On Mon, Nov 1, 2010 at 8:16 PM, Tom Lane wrote:
> This will make the min/max optimization code more visible to the rest of
> the planner in a couple of ways: aside from being called at two places
> not one, it will have some intermediate state that'll have to be kept in
> PlannerInfo, and the "use
Sorry, I messed up and emailed this only to Dimitri.
--- Begin forwarded message from Alvaro Herrera ---
From: Alvaro Herrera
To: Dimitri Fontaine
Date: Wed, 03 Nov 2010 14:13:58 -0300
Subject: Re: [HACKERS] ALTER OBJECT any_name SET SCHEMA name
Excerpts from Dimitri Fontaine's message of mié
Alex Hunsaker writes:
> On Mon, Nov 1, 2010 at 16:59, Tom Lane wrote:
>> Surely, removing the internal name's dependency on the istrigger flag is
>> wrong. Â If you're going to maintain separate hash entries at the pltcl
>> level, why would you want to risk collisions underneath that?
> Good cat
Peter Eisentraut writes:
> On tis, 2010-11-02 at 10:21 -0400, Tom Lane wrote:
>> Do we have a handle on how many buildfarm members this will break?
> I suppose we don't. One way to find out would be to commit just this
> bit
> +# We need the $(eval) function, which is available in GNU make 3.80
On tis, 2010-11-02 at 10:21 -0400, Tom Lane wrote:
> Peter Eisentraut writes:
> > This patch requires GNU make 3.80, because of the above "|" feature and
> > the $(eval) function. Version 3.80 is dated October 2002, so it should
> > be no problem, but I do occasionally read of make 3.79 around he
Heikki Linnakangas writes:
> On 03.11.2010 11:34, Greg Stark wrote:
>> I'm actually not nearly so sanguine about this not affecting existing
>> installations. It means, for example, that anyone who has written
>> monitoring scripts that watch the wal position will see behaviour
>> they're not fami
On Wed, Nov 03, 2010 at 10:24:16AM +0100, Nicolas Barbier wrote:
> 2010/11/2 Kenneth Marshall :
>
> > Given that our hash implimentation mixes the input data well (It does.
> > I tested it.) then a simple rotate-and-xor method is all that should
> > be needed to maintain all of the needed informat
On 03.11.2010 11:34, Greg Stark wrote:
On Tue, Nov 2, 2010 at 2:40 AM, Heikki Linnakangas
wrote:
Back-patch to 9.0. Since this only affects bootstrapping, it makes no
difference to existing installations. We don't need to worry about the
bug in existing installations, because if you've managed
On Tue, Nov 2, 2010 at 2:40 AM, Heikki Linnakangas
wrote:
> Back-patch to 9.0. Since this only affects bootstrapping, it makes no
> difference to existing installations. We don't need to worry about the
> bug in existing installations, because if you've managed to get past the
> initial base backu
2010/11/2 Kenneth Marshall :
> Given that our hash implimentation mixes the input data well (It does.
> I tested it.) then a simple rotate-and-xor method is all that should
> be needed to maintain all of the needed information. The original
> hash function has done the heavy lifting in this case.
The Saturday 30 October 2010 11:05:17, Andres Freund wrote :
> Hi,
>
> This thread died after me not implementing a new version and some potential
> license problems.
>
> I still think its worthwile (and I used it in production for some time) so
> I would like to implement a version fit for the n
27 matches
Mail list logo
