I'm on the way to open a ticket for hash indexes (adding WAL support) anyway:
May I open a ticket for adding GiST support to unlogged tables ?
Stefan
2011/9/14 Stefan Keller :
> Robert,
>
> 2011/9/6 Alexander Korotkov :
>> GiST use serial numbers of operations for concurrency. In current
>> imple
On Sep 12, 2011, at 9:50 AM, Dimitri Fontaine wrote:
>> Thanks to Greg Smith for adding a few bonus ideas I hadn't thought of. What
>> else have you got? I don't think we necessarily have to limit ourselves to
>> core features, BTW: projects like PostGIS and pgAdmin are also clearly
>> popular, an
On Sep 13, 2011, at 3:12 PM, Kevin Grittner wrote:
> And here:
>
> http://www.pgxn.org/tag/foreign%20data%20wrapper/
A shorter URL with more results:
http://www.pgxn.org/tag/fdw
Best,
David
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subsc
This is a review for the patch `Generate column names for
subquery expressions'
(https://commitfest.postgresql.org/action/patch_view?id=632)
Summary
Patch format is in context diff format.
This patch applies cleanly on HEAD and make check suceeded.
It seems have no problem t
This is rebased patch of `Allow encoding specific character
incrementer'(https://commitfest.postgresql.org/action/patch_view?id=602).
Addition to the patch, increment sanity check program for new
functions pg_generic_charinc and pg_utf8_increment is attached.
--
Kyotaro Horiguchi
NTT Open Sourc
On Wed, Sep 14, 2011 at 1:10 AM, Simon Riggs wrote:
> On Tue, Sep 13, 2011 at 2:51 PM, Peter Eisentraut wrote:
>> On tis, 2011-09-13 at 14:46 +0900, Fujii Masao wrote:
>>> Are you still thinking the backward-compatibility (i.e., the
>>> capability to specify recovery parameters in recovery.conf)
On 13 September 2011 15:17, Tom Lane wrote:
> Thom Brown writes:
>> There appears to be a problem with starting Postgres if the SSL key
>> has a passphrase on it.
>
> It's documented that that's unsupported. Given the number of ways to
> start a postmaster, and the fact that many of them are non
Mark Kirkwood writes:
> Recently some pretty significant join optimization improvements have
> made their way into these branches. Are we looking at cutting an 8.4.9
> and 9.0.5 soon?
The plan that was being batted around the core list was to schedule a
set of update releases the last week of S
Josh Kupershmidt writes:
> On Tue, Sep 13, 2011 at 6:29 PM, Tom Lane wrote:
>> Can't reproduce that here, on either 32-bit or 64-bit hardware.
>> However, this sort of issue is often exceedingly sensitive to
>> environment and build options. What's your platform, what did you use
>> for configur
On Tue, Sep 13, 2011 at 6:29 PM, Tom Lane wrote:
> Josh Kupershmidt writes:
>> While trying to test out the "EXPLAIN and nfiltered, take two" patch
>> with its test file "explaintesti", I noticed I was getting a warning
>> message like:
>
>> WARNING: problem in alloc set ExecutorState: detected
Recently some pretty significant join optimization improvements have
made their way into these branches. Are we looking at cutting an 8.4.9
and 9.0.5 soon?
Cheers
Mark
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgr
Josh Kupershmidt writes:
> While trying to test out the "EXPLAIN and nfiltered, take two" patch
> with its test file "explaintesti", I noticed I was getting a warning
> message like:
> WARNING: problem in alloc set ExecutorState: detected write past
> chunk end in block 0x101134e00, chunk 0x101
On Tue, Sep 13, 2011 at 04:18:48AM -0400, Joe Banafato wrote:
> Hi all,
>
> I wrote an implementation of last_value that ignores null values,
> effectively achieving the behavior of last_value( ignore nulls).
> The code is up on BitBucket [1] for the moment. Thoughts:
Just in case of lossage on
While trying to test out the "EXPLAIN and nfiltered, take two" patch
with its test file "explaintesti", I noticed I was getting a warning
message like:
WARNING: problem in alloc set ExecutorState: detected write past
chunk end in block 0x101134e00, chunk 0x101134f38
I got the same warning on un
From: pgsql-hackers-ow...@postgresql.org
[mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Michael Nolan
Sent: Tuesday, September 13, 2011 11:51 AM
To: Joshua D. Drake
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] What Would You Like To Do?
On Tue, Sep 13, 2011 at 12:26 PM, Josh
Dne 12.5.2011 08:54, Greg Smith napsal(a):
> Tomas Vondra wrote:
>> Actually I was not aware of how the buildfarm works, all I
>> knew was there's something like that because some of the hackers mention
>> a failed build on the mailing list occasionally.
>>
>> So I guess this is a good opportunity
Robert,
2011/9/6 Alexander Korotkov :
> GiST use serial numbers of operations for concurrency. In current
> implementation xlog record ids are used in capacity of that numbers. In
> unlogged table no xlog records are produced. So, we haven't serial numbers
> of operations. AFAIK, it's enough to pr
On Mon, Sep 12, 2011 at 8:21 AM, David E. Wheeler wrote:
> So, what do you want to work on? Let me know, I'll do as much match-making
> at the conference as I can.
>
Here is my list:
* Additional approximate string matching functions and index access for them
using gin/gist/spgist.
* Signature ind
On Tue, Sep 13, 2011 at 2:55 PM, Joshua D. Drake wrote:
>
> On 09/13/2011 11:51 AM, Michael Nolan wrote:
>
>
>>The ability to restore a table from a backup file to a different
>>table
>>name in the same database and schema.
>>
>>
>>This can be done but agreed it is not
Rodrigo Gonzalez wrote:
> On 09/13/2011 04:52 PM, Tom Lane wrote:
>> FDW provides the structure within which that will eventually be
>> possible, but there's no Oracle or MySQL wrapper today ...
> They are both listed at wiki
And here:
http://www.pgxn.org/tag/foreign%20data%20wrapper/
-K
On 09/13/2011 04:52 PM, Tom Lane wrote:
Rodrigo Gonzalez writes:
In a perfect world, it would be nice if one could do combined queries
linking a PostgreSQL database with an Oracle one, or a MySQL one,
Can't you do that with FDW that is present in 9.1?
FDW provides the structure within which t
On 09/13/2011 11:51 AM, Michael Nolan wrote:
The ability to restore a table from a backup file to a different
table
name in the same database and schema.
This can be done but agreed it is not intuitive.
Can you elaborate on tha a bit, please? The only way I've
Rodrigo Gonzalez writes:
>> In a perfect world, it would be nice if one could do combined queries
>> linking a PostgreSQL database with an Oracle one, or a MySQL one,
> Can't you do that with FDW that is present in 9.1?
FDW provides the structure within which that will eventually be
possible,
On 09/13/2011 03:51 PM, Michael Nolan wrote:
For example:
A fully integrated ability to query across multiple
databases,possibly
on multiple servers, something Oracle has had for nearly two
decades.
That isn't the approach to take. The fact that Oracle has
On Tue, Sep 13, 2011 at 12:26 PM, Joshua D. Drake wrote:
>
> On 09/13/2011 10:13 AM, Michael Nolan wrote:
>
>> The lists all seem to be focusing on the things that the developers
>> would like to add to PostgreSQL, what about some things that users or
>> ISPs might like to have, and thus perhaps s
Hi all,
I use dbi-link to connect for oracle db 10g and 11g, and
big problem give to me:
example:
select * from table(oracle)
çavân
When dbi-link call information from oracle his show
?cv?an
In pure perl script no have problems too.
Any ideas for help me?
Regards,
Paulo
On 09/13/2011 10:13 AM, Michael Nolan wrote:
The lists all seem to be focusing on the things that the developers
would like to add to PostgreSQL, what about some things that users or
ISPs might like to have, and thus perhaps something that companies might
actually see as worth funding?
Well ju
The lists all seem to be focusing on the things that the developers would
like to add to PostgreSQL, what about some things that users or ISPs might
like to have, and thus perhaps something that companies might actually see
as worth funding?
For example:
A fully integrated ability to query across
On 12 September 2011 05:21, David E. Wheeler wrote:
> Hackers,
>
> Later this week I'm giving a [brief][] for an audience of what I hope will be
> corporate PostgreSQL users that covers how to get a feature developed for
> PostgreSQL. The idea here is that there are a lot of organizations out th
On Tue, 2011-09-13 at 12:34 -0400, Christopher Browne wrote:
> > select int4range(5,2);
> > ERROR: range lower bound must be less than or equal to range upper bound
> >
> > Of course, I won't argue this is a bug, but I was wondering if it wouldn't
> > be handy to allow a
> > 'symmetric' mode in r
On Sep 13, 2011, at 9:43 AM, Hannu Krosing wrote:
> Hannu Krosing / 2ndQuadrant
>
> * more enhancements to pl/python - use real function arguments,
> store modules in database, direct support for postgresql types,
> operators and functions, automatic startup command,
> automatic ORM from
On Sun, 2011-09-11 at 21:21 -0700, David E. Wheeler wrote:
> Hackers,
>
> Later this week I'm giving a [brief][] for an audience of what I
> hope will be corporate PostgreSQL users that covers how to get a
> feature developed for PostgreSQL. The idea here is that there are
> a lot of organizati
On Tue, Sep 13, 2011 at 12:08 PM, Erik Rijkers wrote:
> Just a thought:
>
> select int4range(5,2);
> ERROR: range lower bound must be less than or equal to range upper bound
>
> Of course, I won't argue this is a bug, but I was wondering if it wouldn't be
> handy to allow a
> 'symmetric' mode in
On Tue, Sep 13, 2011 at 2:51 PM, Peter Eisentraut wrote:
> On tis, 2011-09-13 at 14:46 +0900, Fujii Masao wrote:
>> Are you still thinking the backward-compatibility (i.e., the
>> capability to specify recovery parameters in recovery.conf) is
>> required?
>
> I think parameters related to a partic
Hi,
Just a thought:
select int4range(5,2);
ERROR: range lower bound must be less than or equal to range upper bound
Of course, I won't argue this is a bug, but I was wondering if it wouldn't be
handy to allow a
'symmetric' mode in range construction, where, if the first of the pair is
higher
Hi, just tried to upgrade from 9.0 to 9.1 and got this error during
pg_upgrade :
Mismatch of relation id: database "xyz", old relid 465783, new relid 16494
It seems, I get this error on every table as I got it on another table
(which I did not need and deleted) before as well. Schmemas seem to be
m
Hi all,
I wrote an implementation of last_value that ignores null values,
effectively achieving the behavior of last_value( ignore nulls).
The code is up on BitBucket [1] for the moment. Thoughts:
* This isn't on the TODO [2]. Is anyone interested in getting this in
the language? I use this fe
>Yep, that's pretty much what it does, although xmax is actually
>defined as the XID *following* the last one that ended, and I think
>xmin needs to also be in xip, so in this case you'd actually end up
>with xmin = 15, xmax = 22, xip = { 15, 16, 17, 19 }. But you've got
>the basic idea of it.
S
On Sep13, 2011, at 16:25 , Tom Lane wrote:
> Florian Pflug writes:
>> On Sep13, 2011, at 15:05 , Aidan Van Dyk wrote:
>>> Personally, I'ld think that's ripe for bugs. If the contract is that
>>> ret != amount is the "error" case, then don't return -1 for an error
>>> *sometimes*.
>
>> Hm, but i
Peter Eisentraut writes:
> It looks like the --with-system-tzdata case is somewhat broken now in
> initdb:
> creating configuration files ... could not open directory
> "./pg-install/share/timezone": No such file or directory
Sigh. That's what I get for assuming that case was simple enough
On Tue, Sep 13, 2011 at 10:14 AM, Florian Pflug wrote:
>> Personally, I'ld think that's ripe for bugs. If the contract is that
>> ret != amount is the "error" case, then don't return -1 for an error
>> *sometimes*.
>
> Hm, but isn't that how write() works also? AFAIK (non-interruptible) write()
On 13 September 2011 15:17, Tom Lane wrote:
> Thom Brown writes:
>> There appears to be a problem with starting Postgres if the SSL key
>> has a passphrase on it.
>
> It's documented that that's unsupported. Given the number of ways to
> start a postmaster, and the fact that many of them are non
Excerpts from Robert Haas's message of mar sep 13 11:02:51 -0300 2011:
>
> On Fri, Sep 9, 2011 at 5:31 PM, Alvaro Herrera
> wrote:
> > [ multixact complexity ]
>
> I wonder if it's a mistake to be thinking about solving this problem
> by extending the MultiXact mechanism. Pushing xmax out-of-l
Florian Pflug writes:
> On Sep13, 2011, at 15:05 , Aidan Van Dyk wrote:
>> Personally, I'ld think that's ripe for bugs. If the contract is that
>> ret != amount is the "error" case, then don't return -1 for an error
>> *sometimes*.
> Hm, but isn't that how write() works also?
Yeah. It's not p
Thom Brown writes:
> There appears to be a problem with starting Postgres if the SSL key
> has a passphrase on it.
It's documented that that's unsupported. Given the number of ways to
start a postmaster, and the fact that many of them are noninteractive,
I don't think it's very productive for us
On Sep13, 2011, at 15:05 , Aidan Van Dyk wrote:
> On Tue, Sep 13, 2011 at 7:30 AM, Florian Pflug wrote:
>> Sorry for the self-reply. I realized only after hitting send that I
>> got the ENOSPC handling wrong again - we probably ought to check for
>> ENOSPC as well as ret == 0. Also, it seems prefe
On Fri, Sep 9, 2011 at 5:31 PM, Alvaro Herrera
wrote:
> [ multixact complexity ]
I wonder if it's a mistake to be thinking about solving this problem
by extending the MultiXact mechanism. Pushing xmax out-of-line so
that we have room to store tuple information seems expensive,
especially because
Hi,
There appears to be a problem with starting Postgres if the SSL key
has a passphrase on it. The following happens:
Enter PEM pass phrase:
FATAL: could not load private key file "server.key": problems getting password
Starting with "postgres -D /path/to/cluster" returns:
Enter PEM pass phr
On tis, 2011-09-13 at 14:46 +0900, Fujii Masao wrote:
> Are you still thinking the backward-compatibility (i.e., the
> capability to specify recovery parameters in recovery.conf) is
> required?
I think parameters related to a particular recovery, e.g.,
recovery_target_time, fit better into a reco
On ons, 2011-09-07 at 17:16 -0400, Tom Lane wrote:
> Magnus Hagander writes:
> > On Tue, Sep 6, 2011 at 23:52, Robert Haas wrote:
> >> On Tue, Sep 6, 2011 at 5:16 PM, Tom Lane wrote:
> >>> Although there's always more than one way to skin a cat. Consider
> >>> this idea:
> >>>
> >>> 1. The hard
On Tue, Sep 13, 2011 at 7:30 AM, Florian Pflug wrote:
>
> Sorry for the self-reply. I realized only after hitting send that I
> got the ENOSPC handling wrong again - we probably ought to check for
> ENOSPC as well as ret == 0. Also, it seems preferable to return the
> number of bytes actually wri
On Tue, Sep 13, 2011 at 03:02:57PM +0200, Florian Pflug wrote:
> On Sep13, 2011, at 14:58 , k...@rice.edu wrote:
> > It will be interesting to see if there are any performance ramifications to
> > this new write function.
>
> What would those be? For non-interruptible reads and writes, the overhea
On Sep13, 2011, at 14:58 , k...@rice.edu wrote:
> It will be interesting to see if there are any performance ramifications to
> this new write function.
What would those be? For non-interruptible reads and writes, the overhead
comes down to an additional function call (if we don't make pg_write_no
On Tue, Sep 13, 2011 at 01:30:34PM +0200, Florian Pflug wrote:
> On Sep13, 2011, at 13:07 , Florian Pflug wrote:
> > Here's my suggested implementation for pg_write_nointr. pg_read_nointr
> > should be similar
> > (but obviously without the ENOSPC handling)
> >
> >
>
> Sorry for the self-reply.
On Tue, Sep 13, 2011 at 7:49 AM, Amit Kapila wrote:
>>Yep, that's pretty much what it does, although xmax is actually
>>defined as the XID *following* the last one that ended, and I think
>>xmin needs to also be in xip, so in this case you'd actually end up
>>with xmin = 15, xmax = 22, xip = { 15,
On Sep13, 2011, at 13:07 , Florian Pflug wrote:
> Here's my suggested implementation for pg_write_nointr. pg_read_nointr should
> be similar
> (but obviously without the ENOSPC handling)
>
>
Sorry for the self-reply. I realized only after hitting send that I
got the ENOSPC handling wrong again
[CC'ing to the list again - I assume you omitted pgsql-hackers from the
recipient list by accident]
On Sep13, 2011, at 03:00 , George Barnett wrote:
> On 12/09/2011, at 11:39 PM, Florian Pflug wrote:
>> Also, non-interruptible IO primitives are by no means "right". At best,
>> they're
>> a compro
On Mon, Sep 12, 2011 at 10:33 PM, Dermot wrote:
> First off, I hope this approach is not breaking protocol.
>
> I have seen this feature on the todo list:
> http://wiki.postgresql.org/wiki/Todo#Referential_Integrity
>
> It's my understanding that this will allow FK constraints on array
> elements
Update patch.
Changes:
* set 'on' full_page_writes by user (in document)
* read "FROM: XX" in backup_label (in xlog.c)
* check status when pg_stop_backup is executed (in xlog.c)
> Hi, Created a patch in response to comments.
>
>
> * Procedure
> 1. Call pg_start_backup('x') on hot standby
59 matches
Mail list logo
