On Wed, 2011-04-06 at 07:47 +0300, Peter Eisentraut wrote:
> On tis, 2011-04-05 at 16:04 -0700, Joshua D. Drake wrote:
> > Well any libpq app but yes. I actually wonder as to the legitmacy of
> > having both a pgpass and a pg_service. Why not just one of them?
>
> So you can keep passwords in a sa
Hello, Josh.
You wrote:
JB> All,
JB> For 9.1, I'm trying to get beta testing a *bit* more organized in hopes
JB> of shortening the beta period. Since we're not up and running on Django
JB> on the main website yet, and thus I can't make an app for collecting
JB> test reports, I've created a Goog
06.04.2011 02:06, Jan Wieck wrote:
On 4/5/2011 3:24 AM, Vlad Arkhipov wrote:
Hi,
I'm trying to write a C language function that has a REFCURSOR argument.
Could anyone please give me an example of reading from a cursor in C
code?
Sorry, I don't have a code example.
A refcursor data type is
Just to clarify situation a bit. I noticed buffer tree technique while
reseaching
sp-gist and got an idea to use it for improving CREATE INDEX for GiST, which
is what we were looking many times. Alexander is working on his thesis and
this project suits ideally for him and community. Since I and
On tis, 2011-04-05 at 16:04 -0700, Joshua D. Drake wrote:
> Well any libpq app but yes. I actually wonder as to the legitmacy of
> having both a pgpass and a pg_service. Why not just one of them?
So you can keep passwords in a safer place (= less permissions) than the
rest of the connection inform
On Tue, 2011-04-05 at 18:25 -0700, aaronenabs wrote:
> Hi All,
>
> I was wondering if anyone can tell me how i can access the transaction log
> within postgresql 9.0.3.
> I have carried out some updated and deletions within the database and am
> hoping the transaction logs have records of this.
Y
OK, thanks to RhodiumToad on IRC, I was able to determine the cause of
the two reported pg_upgrade problems he saw via IRC. It seems toast
tables have xids and pg_dump is not preserving the toast relfrozenxids
as it should. Heap tables have preserved relfrozenxids, but if you
update a heap row bu
On Mon, Apr 4, 2011 at 3:02 PM, Robert Haas wrote:
> In theory, we have
> documentation that explains this:
>
> http://www.postgresql.org/docs/current/static/docguide-toolsets.html
While we're on the subject..
Attached is a patch against that page suggesting using openjade 1.3,
not 1.4devel as p
Hi All,
I was wondering if anyone can tell me how i can access the transaction log
within postgresql 9.0.3.
I have carried out some updated and deletions within the database and am
hoping the transaction logs have records of this.
Cheers all
--
View this message in context:
http://postgresql.10
Hello
My name is Masanori Yamazaki. I am sending my proposal about
Google Summer Of Code2011. It would be nice if you could give
me your opinion.
・title
Caching query results in pgpool-II
・Synopsis
Pgpool-II has query caching functionality using storage provided by
dedicated PostgreSQL ("sy
On Tue, 2011-04-05 at 18:52 -0400, Aidan Van Dyk wrote:
> On Tue, Apr 5, 2011 at 6:34 PM, Joshua D. Drake
> wrote:
>
> > Bare, useful, but not really friendly nor flexible. I would love to be
> > able to do this:
>
> > [ecom]
> > hostname=
> > port=
> > database=
> > username=
> > password=
>
On Tue, Apr 5, 2011 at 6:34 PM, Joshua D. Drake wrote:
> Bare, useful, but not really friendly nor flexible. I would love to be
> able to do this:
> [ecom]
> hostname=
> port=
> database=
> username=
> password=
That looks a lot like a pg_service file.
> psql ecom
>
> boom, I am in.
>
> Though
On Apr 5, 2011, at 1:59 PM, Aidan Van Dyk wrote:
> Versions are useful for figuring out if I should upgrade packages or
> not. But I believe the extension framework has explicitly made the
> "upgrade" problem a manual one at this point, either taking
> destination versions from the control, or th
On Tue, 2011-04-05 at 15:38 -0700, David E. Wheeler wrote:
> On Apr 5, 2011, at 3:34 PM, Joshua D. Drake wrote:
>
> > boom, I am in.
> >
> > Thoughts?
>
> boom, you have patch?
I'll write it, if I am not going to be tied up for months arguing about
it :P. Thus, I wanted to see if the community
On Tue, Apr 5, 2011 at 4:59 PM, Peter Eisentraut wrote:
> On tis, 2011-04-05 at 14:55 -0400, Robert Haas wrote:
>> and I've also had failures, I believe,
>> from not being connected to the Internet, which is surprising because
>> it's not at all obvious that building the docs should require an
>>
On Apr 5, 2011, at 3:34 PM, Joshua D. Drake wrote:
> boom, I am in.
>
> Thoughts?
boom, you have patch?
David
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 4/5/11 3:34 PM, Joshua D. Drake wrote:
> Bare, useful, but not really friendly nor flexible. I would love to be
> able to do this:
I'll second that I help people troubleshoot a lot of .pgpass files where
the basic issue is getting the fields out of order.
--
Josh Berkus
PostgreSQL Experts In
On Tue, Apr 5, 2011 at 5:52 PM, Andrew Dunstan wrote:
> That doesn't mean we should arbitrarily break compatibility with pl/sql, nor
> that we should feel free to add on warts such as $varname that are
> completely at odds with the style of the rest of the language. That doesn't
> do anything exce
The current structure of .pgpass is:
hostname:port:database:username:password
Bare, useful, but not really friendly nor flexible. I would love to be
able to do this:
If no ini block:
hostname:port:database:username:password
else:
[ecom]
hostname=
port=
database=
username=
password=
[drupal
On 04/05/2011 03:45 PM, Merlin Moncure wrote:
Talking about the standards compliance of functions is a bit silly:
our implementation of functions isn't even close to approximating what
looks to be the standard (according to this at least:
http://farrago.sourceforge.net/design/UserDefinedTypesAn
On Tue, Apr 5, 2011 at 3:47 PM, Peter Eisentraut wrote:
> On tis, 2011-04-05 at 14:45 -0500, Merlin Moncure wrote:
>> Talking about the standards compliance of functions is a bit silly:
>> our implementation of functions isn't even close to approximating what
>> looks to be the standard
>
> That d
On Mon, Apr 4, 2011 at 8:50 PM, Robert Haas wrote:
> OK. Could you briefly describe the algorithm you propose to
> implement, bearing in mind that I haven't read the paper?
>
The technique can be very briefly described in following rules.
M = number of index keys fitting in RAM;
B = number of i
On tis, 2011-04-05 at 14:47 -0400, Tom Lane wrote:
> Supporting user mappings in COMMENT, EXTENSION, etc is not so critical
> that we should push a possibly misdesigned notion of ownership into
> the system for it. Better to take our time and think about that.
>
> (BTW, it might be useful to reco
On tis, 2011-04-05 at 14:55 -0400, Robert Haas wrote:
> and I've also had failures, I believe,
> from not being connected to the Internet, which is surprising because
> it's not at all obvious that building the docs should require an
> Internet connection.
I understand this problem, but just to cl
On Tue, Apr 5, 2011 at 4:51 PM, David E. Wheeler wrote:
>> Of course, I'ld love for extension in 9.1 to provide a basic
>> provides/features for my extension to give, but if that train has
>> already left the station, I don't have much choice ;-(
>
> Yeah, but the way it is doesn't break the abil
On Apr 5, 2011, at 1:42 PM, Aidan Van Dyk wrote:
> Sure, but if you want, the "feature" you can provide can be something like:
> pgtap-1.0 (or any of pgtap-0.2{0,1,2,3,4}).
>
> And if your package is backwards compatable, it could even provide:
> pgtap-0.25
> pgtap-0.24
> pgtap-0.23
I se
On tis, 2011-04-05 at 14:45 -0500, Merlin Moncure wrote:
> Talking about the standards compliance of functions is a bit silly:
> our implementation of functions isn't even close to approximating what
> looks to be the standard
That doesn't mean it couldn't be better in the future. We shouldn't
ta
On Tue, Apr 5, 2011 at 4:20 PM, David E. Wheeler wrote:
> On Apr 4, 2011, at 3:57 PM, Tom Lane wrote:
>
>>> I think the general movement is toward *feature* dependancies. So for
>>> intstance, an extension can specify what *feature* it requires, and
>>> difference "versions" of an extension can p
On Apr 4, 2011, at 3:57 PM, Tom Lane wrote:
>> I think the general movement is toward *feature* dependancies. So for
>> intstance, an extension can specify what *feature* it requires, and
>> difference "versions" of an extension can provide different
>> "features".
>
> Right.
Sounds like a book
All,
For 9.1, I'm trying to get beta testing a *bit* more organized in hopes
of shortening the beta period. Since we're not up and running on Django
on the main website yet, and thus I can't make an app for collecting
test reports, I've created a Google form:
http://tinyurl.com/3gp94er
Please p
2011/4/5 Merlin Moncure :
> On Tue, Apr 5, 2011 at 2:33 PM, Peter Eisentraut wrote:
>> On tis, 2011-04-05 at 15:05 -0400, Robert Haas wrote:
>>> On Tue, Apr 5, 2011 at 1:45 PM, Peter Eisentraut wrote:
>>> > On tis, 2011-04-05 at 11:21 -0500, Merlin Moncure wrote:
>>> >> +1 on using $foo. Even wi
2011/4/5 Peter Eisentraut :
> On tis, 2011-04-05 at 15:05 -0400, Robert Haas wrote:
>> On Tue, Apr 5, 2011 at 1:45 PM, Peter Eisentraut wrote:
>> > On tis, 2011-04-05 at 11:21 -0500, Merlin Moncure wrote:
>> >> +1 on using $foo. Even with the standardization risk I think it's the
>> >> best choic
On Tue, Apr 5, 2011 at 2:33 PM, Peter Eisentraut wrote:
> On tis, 2011-04-05 at 15:05 -0400, Robert Haas wrote:
>> On Tue, Apr 5, 2011 at 1:45 PM, Peter Eisentraut wrote:
>> > On tis, 2011-04-05 at 11:21 -0500, Merlin Moncure wrote:
>> >> +1 on using $foo. Even with the standardization risk I th
On tis, 2011-04-05 at 15:05 -0400, Robert Haas wrote:
> On Tue, Apr 5, 2011 at 1:45 PM, Peter Eisentraut wrote:
> > On tis, 2011-04-05 at 11:21 -0500, Merlin Moncure wrote:
> >> +1 on using $foo. Even with the standardization risk I think it's the
> >> best choice. Prefer $"foo" to ${foo} though.
Merlin Moncure wrote:
On Fri, Mar 25, 2011 at 10:05 PM, David E. Wheeler wrote:
On Mar 25, 2011, at 9:12 PM, Robert Haas wrote:
As I've said before, I believe that the root cause of this problem is
that using the same syntax for variables and column names is a bad
idea in the first place. If
On Tue, Apr 5, 2011 at 3:04 PM, Jesper Krogh wrote:
> I initially set out to put some numbers on "why" the visibillity
> map was important for "select count(*)", primarily to give some
> feedback to Simon Riggs stating:
> "Your tests and discussion remind me that I haven't yet seen any tests
> tha
On Tue, Apr 5, 2011 at 1:45 PM, Peter Eisentraut wrote:
> On tis, 2011-04-05 at 11:21 -0500, Merlin Moncure wrote:
>> +1 on using $foo. Even with the standardization risk I think it's the
>> best choice. Prefer $"foo" to ${foo} though.
>
> What standardization risk? The standard has already exis
Hi.
I initially set out to put some numbers on "why" the visibillity
map was important for "select count(*)", primarily to give some
feedback to Simon Riggs stating:
"Your tests and discussion remind me that I haven't yet seen any tests
that show that index-only scans would be useful for performa
On Tue, Apr 5, 2011 at 7:55 PM, Robert Haas wrote:
>
> I've also had failures, I believe,
> from not being connected to the Internet, which is surprising because
> it's not at all obvious that building the docs should require an
> Internet connection.
Oh, I've run into that and had it cause delay
On Tue, Apr 5, 2011 at 2:18 PM, Peter Eisentraut wrote:
> On mån, 2011-04-04 at 15:02 -0400, Robert Haas wrote:
>> AFAICT, the biggest problem with our existing toolchain is that it's
>> hard for some people to get it working. In theory, we have
>> documentation that explains this:
>>
>> http://w
Robert Haas writes:
> On Tue, Apr 5, 2011 at 11:25 AM, Robert Haas wrote:
>> I am also wondering about the open issue of supporting comments to
>> SQL/MED objects. I thought that was pretty straightforward, but given
>> that it took me three commits to get servers and foreign data wrappers
>> sq
On mån, 2011-04-04 at 19:26 +0200, Susanne Ebrecht wrote:
> Honestly, for German I don't mind yet if it is XML or SGML. XML might
> be better in future for maintenance tools.
>
> Anyway, I figured out there is another argument for XML:
>
> My information is that DocBook 5.0 won't support SGML any
Robert Haas writes:
> On Tue, Apr 5, 2011 at 6:03 AM, Shigeru HANADA
> wrote:
>> * The comment_user_mapping_core.patch includes syntax support, catalog
>> manipulation, pg_dump support, documents and regression tests.
> I don't think it's going to fly to add a function
> pg_usermapping_ownerchec
Excerpts from Gabriele Bartolini's message of lun abr 04 16:47:26 -0400 2011:
> Il 04/04/11 22:26, Robert Haas ha scritto:
> > I think you still need to update Solution.pm to match.
> >
> Here it is, including change of 3 'Id' attributes (I made them lowercase).
Pushed this one also.
--
Álvaro
On mån, 2011-04-04 at 15:08 -0400, Tom Lane wrote:
> One thing I'd like to know is whether docbook v5 is any more
> portable/easier to install.
I don't see why. It's just a newer version of the same thing.
If you change the sources to XML and switch to the XSL toolchain, you
don't have to instal
On mån, 2011-04-04 at 15:02 -0400, Robert Haas wrote:
> AFAICT, the biggest problem with our existing toolchain is that it's
> hard for some people to get it working. In theory, we have
> documentation that explains this:
>
> http://www.postgresql.org/docs/current/static/docguide-toolsets.html
>
On mån, 2011-04-04 at 17:08 -0400, Andrew Dunstan wrote:
>
> On 04/04/2011 04:41 PM, Peter Eisentraut wrote:
> > My not yet complete attempt at doing a Windows build produces several of
> > these warnings during the build phase:
> >
> > Hash %ENV missing the % in argument 1 of each() at -e li
On tis, 2011-04-05 at 11:21 -0500, Merlin Moncure wrote:
> +1 on using $foo. Even with the standardization risk I think it's the
> best choice. Prefer $"foo" to ${foo} though.
What standardization risk? The standard has already existed for >10
years and is widely implemented.
--
Sent via pgs
On mån, 2011-04-04 at 19:49 +0900, Shigeru HANADA wrote:
> 1) Who can comment on a user mapping?
I'm not sure that it's necessary to allow commenting on user mappings.
You can't comment on role grants either, for example. They're somewhat
similar things.
--
Sent via pgsql-hackers mailing list
On 4/5/2011 3:24 AM, Vlad Arkhipov wrote:
Hi,
I'm trying to write a C language function that has a REFCURSOR argument.
Could anyone please give me an example of reading from a cursor in C code?
Sorry, I don't have a code example.
A refcursor data type is basically a string, containing the na
On Tue, Apr 5, 2011 at 11:25 AM, Robert Haas wrote:
> I am also wondering about the open issue of supporting comments to
> SQL/MED objects. I thought that was pretty straightforward, but given
> that it took me three commits to get servers and foreign data wrappers
> squared away and then it turn
On Tue, Apr 5, 2011 at 6:03 AM, Shigeru HANADA
wrote:
> On Tue, 05 Apr 2011 13:37:48 +0900
> Shigeru HANADA wrote:
>> On Mon, 4 Apr 2011 12:47:18 -0400
>> Robert Haas wrote:
>> > BTW, I think you can merge patches 0001 to 0004 into a single patch.
>>
>> They were separated just for review, so I'
On Fri, Mar 25, 2011 at 10:05 PM, David E. Wheeler wrote:
> On Mar 25, 2011, at 9:12 PM, Robert Haas wrote:
>
>>
>> As I've said before, I believe that the root cause of this problem is
>> that using the same syntax for variables and column names is a bad
>> idea in the first place. If we used $f
On Tue, Apr 5, 2011 at 9:49 AM, Jim Nasby wrote:
> On Mar 28, 2011, at 9:48 AM, Merlin Moncure wrote:
>> On Mon, Mar 28, 2011 at 9:29 AM, Kevin Grittner
>> wrote:
>>> Tom Lane wrote:
>>>
The major problem with all of this is that the bgwriter has no
idea which buffers contain heap page
On 05.04.2011 13:19, Marti Raudsepp wrote:
On Fri, Apr 1, 2011 at 14:24, Heikki Linnakangas
wrote:
We sometimes transform IN-clauses to a list of ORs:
postgres=# explain SELECT * FROM foo WHERE a IN (b, c);
QUERY PLAN
Seq Scan on foo (cost=0.00..39.10 rows=19 width=12
On Tue, Apr 5, 2011 at 11:12 AM, Tom Lane wrote:
> "Kevin Grittner" writes:
>> Robert Haas wrote:
>>> Dimitri Fontaine wrote:
Maybe it's just me, but I'm struggling to understand current
community processes and decisions.
>
>>> Well, I've already spent a fair amount of time trying to
On Mar 28, 2011, at 3:18 PM, Peter Eisentraut wrote:
> On lör, 2011-03-26 at 09:41 -0400, Robert Haas wrote:
>> You can't be guaranteed that they won't standardize something
>> incompatible no matter what we do. We could choose to do it as you've
>> proposed and they could then standardize some we
On Mar 28, 2011, at 10:43 AM, Tom Lane wrote:
> Andrew Dunstan writes:
>> On 03/28/2011 11:14 AM, Tom Lane wrote:
I think the most straightforward and reliable fix for this would be to
forbid recursive containment of a rowtype in itself --- ie, the first
ALTER should have been rejec
On Mar 28, 2011, at 9:48 AM, Merlin Moncure wrote:
> On Mon, Mar 28, 2011 at 9:29 AM, Kevin Grittner
> wrote:
>> Tom Lane wrote:
>>
>>> The major problem with all of this is that the bgwriter has no
>>> idea which buffers contain heap pages. And I'm not convinced it's
>>> a good idea to try to
"Kevin Grittner" writes:
> Robert Haas wrote:
>> Dimitri Fontaine wrote:
>>> Maybe it's just me, but I'm struggling to understand current
>>> community processes and decisions.
>> Well, I've already spent a fair amount of time trying to explain
>> my understanding of it, and for my trouble I g
Robert Haas wrote:
> Dimitri Fontaine wrote:
>> Maybe it's just me, but I'm struggling to understand current
>> community processes and decisions.
> Well, I've already spent a fair amount of time trying to explain
> my understanding of it, and for my trouble I got accused of being
> long-wind
Alexander Korotkov writes:
> On Tue, Apr 5, 2011 at 5:05 PM, Robert Haas wrote:
>> I am probably being stupid here, but doesn't the number of links to
>> rows grow proportionately to the number of n-grams?
> Number of links to rows grow proportionally to total number of extracted
> q-grams, but
Dan Ports writes:
> On Mon, Apr 04, 2011 at 07:04:59PM -0400, Robert Haas wrote:
>> On Mon, Apr 4, 2011 at 6:41 PM, Stephen Frost wrote:
>>> What'd be horribly useful would be the pid and the *time* that the lock
>>> was taken.
>> Well, I don't think we're likely to redesign pg_locks at this poi
Reading through this thread...
On Sat, Mar 26, 2011 at 12:36 AM, Tom Lane wrote:
> ** Selecting a field from a record-returning function's output.
> Currently, we'll use the field's declared collation; except that
> if the field has default collation, we'll replace that with the common
> collatio
For what it's worth it seems to me this patch makrmes it at least
conceptually easier to add new modes like Simon plans, not harder. It's
worth making sure we pick names that still make sense when the new
functionality goes in of course.
The other question is whether it's "fair" that one kind of p
On Wed, Mar 30, 2011 at 9:32 PM, Noah Misch wrote:
> On Wed, Mar 30, 2011 at 07:50:12PM +0300, Peter Eisentraut wrote:
>> On tor, 2011-02-10 at 06:31 +0200, Peter Eisentraut wrote:
>> > > ERROR: cannot drop column from typed table
>> > >
>> > > which probably is because test_type2 has a dropped c
On Tue, Apr 5, 2011 at 5:05 PM, Robert Haas wrote:
> I am probably being stupid here, but doesn't the number of links to
> rows grow proportionately to the number of n-grams?
Number of links to rows grow proportionally to total number of extracted
q-grams, but not proportionally to number of uni
On Tue, Apr 5, 2011 at 1:10 AM, Joseph Adams wrote:
> Attached is an updated version of the patch to allow conversion of
> int4/int8 directly to money. I added overflow checks, dropped
> int2->cash, and updated the documentation.
Excellent, thanks.
My only gripe is that I don't think we should
Aidan Van Dyk writes:
> I think the general movement is toward *feature* dependancies. So for
> intstance, an extension can specify what *feature* it requires, and
> difference "versions" of an extension can provide different
> "features".
That sounds like what Emacs is doing too.
> But checkin
On Saturday, April 02, 2011 09:12:32 PM Tom Lane's cat walking on the keyboard
wrote:
>
> It's possible that we need to adjust PG's dtrace code to support the
> FreeBSD implementation, but if so we'd need advice from an expert on
> what needs to be changed.
Thanks.
In the meantime I attached a
On Tue, Apr 5, 2011 at 8:41 AM, Alexander Korotkov wrote:
> For example, here is distribution of q-grams count in 120 Mb of dblp paper
> titles (pretty large dataset).
> q count
> 2 7218
> 3 115107
> 4 589428
> 5 1648453
> 6 3336685
> Number of 5-grams if about 15x larger than number of 3-g
For example, here is distribution of q-grams count in 120 Mb of dblp paper
titles (pretty large dataset).
q count
27218
3 115107
4 589428
5 1648453
6 3336685
Number of 5-grams if about 15x larger than number of 3-grams. But most part
of index space will be occupied by links to the rows(abou
On Tue, Apr 5, 2011 at 3:56 PM, Robert Haas wrote:
> So with q=5, the index will be approximately 10x larger than with q=3.
> Maybe that's OK, I'm not sure. But it is a big difference.
Not whole index will be approximately 10x larger, but only entries pages
number (which contains btree on gin
On Tue, Apr 5, 2011 at 4:52 AM, Alexander Korotkov wrote:
> On Mon, Apr 4, 2011 at 9:01 PM, Robert Haas wrote:
>>
>> On Mon, Apr 4, 2011 at 12:38 PM, Alexander Korotkov
>> wrote:
>> > relatively small when q <= 5. Accordingly, I think we should expect
>> > indexes
>> > to be usable with at least
On Tue, Apr 5, 2011 at 3:53 AM, Dimitri Fontaine wrote:
> Robert Haas writes:
>>> The attached patch merges synchronous_replication into synchronous_commit.
>> Committed
>
> Without discussion? I would think that this patch is stepping on the
> other one toes and that maybe would need to make a
On Fri, Apr 1, 2011 at 14:24, Heikki Linnakangas
wrote:
> We sometimes transform IN-clauses to a list of ORs:
>
> postgres=# explain SELECT * FROM foo WHERE a IN (b, c);
> QUERY PLAN
> Seq Scan on foo (cost=0.00..39.10 rows=19 width=12)
> Filter: ((a = b) OR (a = c))
>
> B
On Tue, 05 Apr 2011 13:37:48 +0900
Shigeru HANADA wrote:
> On Mon, 4 Apr 2011 12:47:18 -0400
> Robert Haas wrote:
> > BTW, I think you can merge patches 0001 to 0004 into a single patch.
>
> They were separated just for review, so I'll post revised and unified
> patch ASAP.
Please find attached
On Mon, Apr 4, 2011 at 9:01 PM, Robert Haas wrote:
> On Mon, Apr 4, 2011 at 12:38 PM, Alexander Korotkov
> wrote:
> > relatively small when q <= 5. Accordingly, I think we should expect
> indexes
> > to be usable with at least with q = 5.
>
> I defer to your opinion on this, since you know more
Heikki Linnakangas writes:
>> No, sorry about confusion. One GUC is better. What I'm wondering is
>> why commit it *now*, because I think we didn't yet decide on what the
>> supported behaviors supported in 9.1 should be.
>
> What do you mean by "supported behaviors"?
Well, I'm thinking about S
On 05.04.2011 11:31, Dimitri Fontaine wrote:
Fujii Masao writes:
Hmm.. I think that we reached the consensus about merging two GUCs
in previous discussion. You argue that synchronization level should be
controlled in separate two parameters?
No, sorry about confusion. One GUC is better. Wha
Fujii Masao writes:
> Hmm.. I think that we reached the consensus about merging two GUCs
> in previous discussion. You argue that synchronization level should be
> controlled in separate two parameters?
No, sorry about confusion. One GUC is better. What I'm wondering is
why commit it *now*, bec
On Tue, Apr 5, 2011 at 4:53 PM, Dimitri Fontaine wrote:
> Hi,
>
> Robert Haas writes:
>>> The attached patch merges synchronous_replication into synchronous_commit.
>> Committed
>
> Without discussion? I would think that this patch is stepping on the
> other one toes and that maybe would need to
Hi,
Robert Haas writes:
>> The attached patch merges synchronous_replication into synchronous_commit.
> Committed
Without discussion? I would think that this patch is stepping on the
other one toes and that maybe would need to make a decision about sync
rep behavior before to commit this change
Hi,
I'm trying to write a C language function that has a REFCURSOR argument.
Could anyone please give me an example of reading from a cursor in C code?
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
84 matches
Mail list logo
