Peter Eisentraut writes:
> Seems like a reasonable solution, although I've never heard
> of .emacs.custom; my emacsen have always written their custom settings
> somewhere in the middle of the .emacs proper.
See (info "(emacs) Saving Customizations") and add the following to your
setup:
(set
Alvaro Herrera writes:
> Does this mean that the control file should contain a version number in
> the filename? Otherwise, I don't see how you'd have more than one
> version of the control file.
>
> Also, if upgrading is necessary, there will need to be one "upgrade"
> control file that says how
Dimitri Fontaine writes:
> cat postgresql.conf.d/work_mem
> 16MB
> This database needs at least such a value.
> Note it's overridden in some ROLEs setup.
>
>
> With such a format (name is filename, value is first line content's,
> rest is comments), it's easy to preserve comments and have them mac
Excerpts from Bruce Momjian's message of mié oct 13 15:32:22 -0300 2010:
> We have a database specification in .pgpass:
>
> hostname:port:database:username:password
>
> What is the purpose of 'database' since username/password combinations
> are global, not per database? I would like to docu
Excerpts from Itagaki Takahiro's message of mié oct 13 23:03:16 -0300 2010:
> On Thu, Oct 14, 2010 at 10:23 AM, Robert Haas wrote:
> > On Wed, Sep 29, 2010 at 3:59 AM, Pavel Stehule
> > wrote:
> >> [ updated patch, in response to a review from Itagaki Takahiro ]
> >
> > This patch appears to be
On Wed, 13 Oct 2010 21:01:06 -0400, Robert Haas
wrote:
> Is this a JDBC patch or a PG patch? Are we tracking JDBC patches
> using the CF app?
It is JDBC patch. I will clean it and submit on this site. I didn't know
about such application and such process.
--
Radosław Smogura
http://www.
* Bruce Momjian wrote:
Thom Brown wrote:
Also:
SELECT alias, description, token FROM ts_debug('myname+prior...@gmail.com');
Yields:
alias | description | token
---+-+
asciiword | Word, all ASCII | myname
blank | Space symb
On 14/10/10 12:14, Itagaki Takahiro wrote:
Which solution is better? Or, another idea?
This does seem to be an new bug in previously working code. While any
solution that fixes the problem is good, it might pay to look the code
that worked before. As reported, it worked for ecpg (Postgr
On Tue, Oct 5, 2010 at 4:57 PM, Bernd Helmle wrote:
> --On 30. September 2010 10:12:48 +0200 Bernd Helmle
> wrote:
>
>> Yeah, there where some changes in the meantime to the master which
>> generate some merge failures...will provide a new version along with
>> other fixes soon
>
> Here's a new p
Hello
2010/10/14 Itagaki Takahiro :
>> Let's make format support %s, %i, and %l, as well as
>> allowing things like %$3l (meaning, escape the third argument as a
>> literal and interpolate here), and call it good.
>
> Your idea is:
> % [ $ pos ] format -- ex. %$3l , %l
> Escapes: %% => %
>
> Ju
On Thu, Jun 24, 2010 at 8:19 AM, Michael Meskes wrote:
> On Thu, Jun 24, 2010 at 12:04:30PM +0300, Heikki Linnakangas wrote:
>> Is there a reason not to enable it by default? I'm a bit worried
>> that it will receive no testing if it's not always on.
>
> Yes, there is a reason, namely that you don
Tom Lane wrote:
> > I maintain that if someone else whacked around one of your commits the
> > way you whacked this around, you'd bite their head off.
>
> I apologize if I offended you. I hadn't believed that there was any
> particular consensus on how this script ought to behave; I thought
> it
On Thu, Oct 14, 2010 at 3:52 PM, David Newall
wrote:
> This does seem to be an new bug in previously working code. While any
> solution that fixes the problem is good, it might pay to look the code that
> worked before. As reported, it worked for ecpg (PostgreSQL 8.3.8) 4.4.1.
It works on 8.3,
On 10/13/2010 02:32 PM, Bruce Momjian wrote:
We have a database specification in .pgpass:
hostname:port:database:username:password
What is the purpose of 'database' since username/password combinations
are global, not per database? I would like to documents its purpose.
If you use
> Let's make format support %s, %i, and %l, as well as
> allowing things like %$3l (meaning, escape the third argument as a
> literal and interpolate here), and call it good.
Your idea is:
% [ $ pos ] format -- ex. %$3l , %l
Escapes: %% => %
Just for information, $ and pos are reversed in C
On Wed, Oct 13, 2010 at 10:03 PM, Itagaki Takahiro
wrote:
> On Thu, Oct 14, 2010 at 10:23 AM, Robert Haas wrote:
>> On Wed, Sep 29, 2010 at 3:59 AM, Pavel Stehule
>> wrote:
>>> [ updated patch, in response to a review from Itagaki Takahiro ]
>>
>> This patch appears to be waiting for a second r
I'll post it sometime tomorrow...
Thanks
Andrew
On Wed, Oct 13, 2010 at 9:25 PM, Robert Haas wrote:
> On Tue, Oct 5, 2010 at 4:57 PM, Bernd Helmle wrote:
>> --On 30. September 2010 10:12:48 +0200 Bernd Helmle
>> wrote:
>>
>>> Yeah, there where some changes in the meantime to the master which
>>
On 13 October 2010 23:17, Robert Haas wrote:
> On Wed, Oct 13, 2010 at 7:33 AM, Andrew Dunstan wrote:
>> Sorry, got distracted. Here's a new patch that fixes the above and also
>> contains some documentation.
>
> Someone want to review this and (hopefully) mark it Ready for
> Committer? I see th
On Tue, Oct 12, 2010 at 11:50 PM, Robert Haas wrote:
> There's another problem here we should think about, too. Suppose you
> have a master and two standbys. The master dies. You promote one of
> the standbys, which turns out to be behind the other. You then
> repoint the other standby at the
On Wed, Oct 13, 2010 at 7:33 AM, Andrew Dunstan wrote:
> Sorry, got distracted. Here's a new patch that fixes the above and also
> contains some documentation.
Someone want to review this and (hopefully) mark it Ready for
Committer? I see that Brendan Jurd is the reviewer of record in the
CF app
On Wed, Oct 13, 2010 at 5:54 PM, Robert Haas wrote:
> Or to put it more bluntly - what is the "problem with planner and hash
> agg" that all of these functions need to solve? And why does it need
> a flag in pg_proc? Why can't't we leave it to the individual
> functions to perform a sort of one
Hi,
--
if (recoveryTarget == RECOVERY_TARGET_XID)
snprintf(buffer, sizeof(buffer),
"%s%u\t%s\t%s transaction %u\n",
(srcfd < 0) ? "" : "\n",
parentTLI,
On Wed, Oct 13, 2010 at 21:21, Peter Eisentraut wrote:
> This surprised me:
>
> psql -p 5 -h localhost
> psql: could not connect to server: Connection refused
> Is the server running on host "localhost" and accepting
> TCP/IP connections on port 5?
> could not connect to serv
Hi,
It takes nonsensically extra several seconds to shut down the standby server.
This is because the startup process cannot respond immediately the SIGTERM
signal sent by postmaster for the shutdown while it's sleeping on WaitLatch.
This delays the shutdown for up to the sleep time on WaitLatch (
> We have a database specification in .pgpass:
>
> hostname:port:database:username:password
>
> What is the purpose of 'database' since username/password combinations
> are global, not per database? I would like to documents its purpose.
There is the GUC parameter db_user_namespace. Just fo
On Wed, Oct 13, 2010 at 6:56 AM, Pavel Stehule wrote:
> 2010/10/13 Pavel Stehule :
>> 2010/10/13 Peter Eisentraut :
>>> On mån, 2010-10-11 at 20:46 +0200, Pavel Stehule wrote:
The problem is in interface. The original patch did it, but I removed
it. We cannot to unsure immutability of so
Ok, it seems impossible to do that by using any public interfaces
currently available in PostgreSQL 9.0. I will create a custom C
function to be distributed along with pgpool-II.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
> H
Hi
I am a keen Postgres user and I run my local PUG (JNBPUG in Gauteng,
South Africa), but I have found the idea of contributing on a code
level daunting.
Having read the many warnings along the lines of "It's still on the
todo because it isn't trivial" I have identified what I believe is a
manag
Hi,
Robert Haas írta:
> On Thu, Jun 24, 2010 at 8:19 AM, Michael Meskes wrote:
>
>> On Thu, Jun 24, 2010 at 12:04:30PM +0300, Heikki Linnakangas wrote:
>>
>>> Is there a reason not to enable it by default? I'm a bit worried
>>> that it will receive no testing if it's not always on.
>>>
Dimitri Fontaine writes:
> Ok, now, some people want to still be able to edit the files by hand
I wonder if providing a system function to load some configuration
option from a file, using the current parser, would do it:
SELECT pg_load_conf('path/to/filename.conf', permament => true);
Of cou
On 14 October 2010 08:45, Robert Haas wrote:
> Is someone working on a patch?
Yes, I will prepare a patch to get us started.
Cheers,
BJ
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Wed, Oct 13, 2010 at 2:27 PM, Kevin Grittner
wrote:
> Rados*aw Smogura wrote:
>
>> I updated patch to latets CVS version, I didn't have time to
>> remove some trashes from it.
>>
>> If something will be wrong with patch, give a feedback.
>
> I skimmed it and agree that it is the right general a
2010/10/14 Robert Haas :
> On Wed, Oct 13, 2010 at 10:03 PM, Itagaki Takahiro
> wrote:
>> On Thu, Oct 14, 2010 at 10:23 AM, Robert Haas wrote:
>>> On Wed, Sep 29, 2010 at 3:59 AM, Pavel Stehule
>>> wrote:
[ updated patch, in response to a review from Itagaki Takahiro ]
>>>
>>> This patch a
2010/10/14 Robert Haas :
> On Wed, Oct 13, 2010 at 6:56 AM, Pavel Stehule
> wrote:
>> 2010/10/13 Pavel Stehule :
>>> 2010/10/13 Peter Eisentraut :
On mån, 2010-10-11 at 20:46 +0200, Pavel Stehule wrote:
> The problem is in interface. The original patch did it, but I removed
> it. We
On Wed, Sep 29, 2010 at 3:59 AM, Pavel Stehule wrote:
> [ updated patch, in response to a review from Itagaki Takahiro ]
This patch appears to be waiting for a second round of review.
Itagaki-san, are you planning to do that?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterpri
On Wed, Sep 29, 2010 at 2:44 AM, Greg Smith wrote:
> Starting looking at the latest MERGE patch from Boxuan here tonight. The
> regression tests pass for me here, good starting sign. I expect to move onto
> trying to break it more creatively next, then onto performance tests.
> Nothing much more e
On Tue, Oct 12, 2010 at 2:27 AM, Shigeru HANADA
wrote:
> Thanks for the review!
> I'll finish the SQL/MED patch by applying your comments.
I think this patch has gotten as much review as we can reasonably give
it this CommitFest (which is about to end), so I'm going to mark it
Returned with Feedb
I would like to ask in which future version of postgresql knngist is planned
to be included. Is there any possibility to be included in 9.1?
On Fri, Sep 24, 2010 at 1:57 AM, Peter Eisentraut wrote:
> On fre, 2010-09-24 at 09:32 +0900, Itagaki Takahiro wrote:
>> On Wed, Sep 22, 2010 at 10:29 PM, Peter Eisentraut wrote:
>> >> We could support it also on MSVC.
>> >> http://msdn.microsoft.com/en-us/library/a7cwbx4t(v=VS.90).aspx --
>> >>
On Tue, Oct 12, 2010 at 8:28 AM, Fujii Masao wrote:
> On Sat, Oct 9, 2010 at 10:04 AM, Brendan Jurd wrote:
>> Hi folks,
>>
>> I have just set up HS+SR for the first time, and for the most part,
>> the docs were excellent. The one exception for me was the discussion
>> of archive_cleanup_command.
Am 14.10.2010 08:52, schrieb David Newall:
On 14/10/10 12:14, Itagaki Takahiro wrote:
Which solution is better? Or, another idea?
This does seem to be an new bug in previously working code. While any
solution that fixes the problem is good, it might pay to look the code
that worked before. As
On Thu, Oct 14, 2010 at 11:10 AM, Tatsuo Ishii wrote:
> Ok, it seems impossible to do that by using any public interfaces
> currently available in PostgreSQL 9.0. I will create a custom C
> function to be distributed along with pgpool-II.
Could you submit the function for 9.1? Thanks :-)
--
Ita
On Wed, Oct 13, 2010 at 5:22 AM, Fujii Masao wrote:
> On Wed, Oct 13, 2010 at 3:50 PM, Robert Haas wrote:
>> There's another problem here we should think about, too. Suppose you
>> have a master and two standbys. The master dies. You promote one of
>> the standbys, which turns out to be behind
On Thu, Oct 14, 2010 at 10:23 AM, Robert Haas wrote:
> On Wed, Sep 29, 2010 at 3:59 AM, Pavel Stehule
> wrote:
>> [ updated patch, in response to a review from Itagaki Takahiro ]
>
> This patch appears to be waiting for a second round of review.
> Itagaki-san, are you planning to do that?
I can
On Thu, Oct 14, 2010 at 11:18 AM, Greg Stark wrote:
> Why don't the usual protections kick in here? The new record read from
> the location the xlog reader is expecting to find it has to have a
> valid CRC and a correct back pointer to the previous record.
Yep. In most cases, those protections se
Hello, Bruce.
You wrote:
BM> We have a database specification in .pgpass:
BM> hostname:port:database:username:password
BM> What is the purpose of 'database' since username/password combinations
BM> are global, not per database? I would like to documents its purpose.
BM> --
BM> Bruc
On Wed, Oct 13, 2010 at 10:37 PM, Greg Stark wrote:
> On Wed, Oct 13, 2010 at 5:54 PM, Robert Haas wrote:
>> Or to put it more bluntly - what is the "problem with planner and hash
>> agg" that all of these functions need to solve? And why does it need
>> a flag in pg_proc? Why can't't we leave
On Wed, Oct 13, 2010 at 10:18 PM, Greg Stark wrote:
> On Tue, Oct 12, 2010 at 11:50 PM, Robert Haas wrote:
>> There's another problem here we should think about, too. Suppose you
>> have a master and two standbys. The master dies. You promote one of
>> the standbys, which turns out to be behin
On Thu, Oct 14, 2010 at 6:53 AM, Michael Meskes wrote:
> Am 14.10.2010 08:52, schrieb David Newall:
>>
>> On 14/10/10 12:14, Itagaki Takahiro wrote:
>>>
>>> Which solution is better? Or, another idea?
>>
>> This does seem to be an new bug in previously working code. While any
>> solution that fixe
On Thu, Oct 14, 2010 at 2:59 AM, Radosław Smogura
wrote:
> On Wed, 13 Oct 2010 21:01:06 -0400, Robert Haas
> wrote:
>> Is this a JDBC patch or a PG patch? Are we tracking JDBC patches
>> using the CF app?
>
> It is JDBC patch. I will clean it and submit on this site. I didn't know
> about such a
On Thu, Oct 14, 2010 at 2:25 AM, Itagaki Takahiro
wrote:
>> Let's make format support %s, %i, and %l, as well as
>> allowing things like %$3l (meaning, escape the third argument as a
>> literal and interpolate here), and call it good.
>
> Your idea is:
> % [ $ pos ] format -- ex. %$3l , %l
> Es
On Mon, Oct 11, 2010 at 7:42 AM, David Newall
wrote:
> Trivial program to demonstrate problem:
>
> main() {
> ECPGdebug(1,stderr);
> exec sql connect to postgres;
> exec sql set autocommit to off;
> exec sql start transaction;
> exec sql savepoint s;
> exec sql rollback to s;
>
On 10/14/2010 08:25 AM, Robert Haas wrote:
IMHO, I like {} syntax as like as C# because the format strings are extensible.
{ pos [ : format ] } -- ex {3:l}, {3} (, and {l} could be also supported)
Escapes: {{ => {, }} => }
My personal preference (and Pavel's, I guess) is to use the C-l
Robert Haas wrote:
> Is this a JDBC patch or a PG patch? Are we tracking JDBC patches
> using the CF app?
If this were the only patch for setQueryTimeout in front of us I
probably wouldn't have suggested that, but this thread started with a
patch proposal to implement the same JDBC feature thr
Below is my review of the latest iteration of the "Extend NOT NULL
Representation to pg_constraint" patch found here:
http://archives.postgresql.org/message-id/e57a252dfd60c1fca9173...@amenophis
Thanks
Andrew
2010/10/14 Alastair Turner :
> I am proposing altering psql to raise certain errors and exit before
> prompting for a password. These errors would have to be on items which
> didn't leak any information, my current list is:
> - Does the input file (-f) exist and is it readable
> - Do paths to the
Robert Haas wrote:
Greg, are you still working on a review of this patch?
Yes, just had more distractions while coming to speed up on this area
than I'd hoped. I'll get a second round of looking at this done by the
weekend.
--
Greg Smith, 2ndQuadrant US g...@2ndquadrant.com Baltimore, M
Dimitri Fontaine writes:
> Allow me to insist on this some more, because there's something
> important going on here. The other proposal (.auto) have a major failure
> mode that I don't think is acceptable.
> SET PERMANENT work_mem TO '8 MB';
> select pg_reload_conf();
> There's simply no wa
On Thu, Oct 14, 2010 at 06:09:35AM +0200, Dennis Bj??rklund wrote:
> > We have a database specification in .pgpass:
> >
> > hostname:port:database:username:password
> >
> > What is the purpose of 'database' since username/password combinations
> > are global, not per database? I would like to
Alastair Turner writes:
> I am proposing altering psql to raise certain errors and exit before
> prompting for a password. These errors would have to be on items which
> didn't leak any information, my current list is:
> - Does the input file (-f) exist and is it readable
> - Do paths to the out
On Thu, Oct 14, 2010 at 4:05 PM, Tom Lane wrote:
> Alastair Turner writes:
>> I am proposing altering psql to raise certain errors and exit before
>> prompting for a password. These errors would have to be on items which
>> didn't leak any information, my current list is:
>> - Does the input fil
Dimitri Fontaine writes:
> I wonder if providing a system function to load some configuration
> option from a file, using the current parser, would do it:
> SELECT pg_load_conf('path/to/filename.conf', permament => true);
That seems like a pretty bizarre idea. The settings wouldn't be
persist
I found PostgreSQL accepts UNION DISTINCT but documents don't mention it.
http://www.postgresql.org/docs/9.0/static/sql-select.html#SQL-UNION
select_statement UNION [ ALL ] select_statement
UNION DISTINCT is nothing more than UNION itself, but gram.y
definitely accept it and the SQL standard des
On Thu, Oct 14, 2010 at 6:53 AM, Michael Meskes wrote:
You seem to be answering to an email that I didn't see and couldn't find in
the archive either. Was it send in private or to the list? If it went to the
list I might be lagging behind.
On 14/10/10 22:51, Robert Haas wrote:
I didn't g
Tom Lane writes:
> Um, other than "show work_mem" or "select from pg_settings"?
>
> The fact is that you cannot know the active value anyway without
> checking, because what you did with SET PERMANENT might be overridden
> in various session-local ways. The proposal for hand-edited versus
> machi
Tom Lane writes:
>> SELECT pg_load_conf('path/to/filename.conf', permament => true);
>
> That seems like a pretty bizarre idea. The settings wouldn't be
> persistent would they? Or are you proposing this as a substitute
> way of providing input for SET PERMANENT? If so what's the value?
Yeah
Excerpt from Hitoshi Harada - Thu, Oct 14, 2010
at 4:32 PM:
> Just for information, did you pick this topic from TODO
> list? If so, could you attach links to the entry or to some related
> former thread? And in general it is encouraged that you'd better send
> one feature per a patch, in order fo
Hitoshi Harada writes:
> UNION DISTINCT is nothing more than UNION itself, but gram.y
> definitely accept it and the SQL standard describes it as well. Should
> we add DISTINCT to docs?
I think it'd be hard to describe without confusing people, because
while DISTINCT is a noise word there, it's d
Dimitri Fontaine writes:
> I understand that. I just think there are already too many sources for
> GUCs and would welcome that there's a single possible source file with a
> complete remote editing feature.
[ shrug... ] So don't use the option of hand-editing postgresql.conf.
You're not being f
Tom Lane writes:
> [ shrug... ] So don't use the option of hand-editing postgresql.conf.
> You're not being forced to do that, and on the other side of the coin,
> you shouldn't think that you get to force people who'd rather hand-edit
> to change their habits.
Sure. I just lose comments. I'll l
> On Thu, Oct 14, 2010 at 11:10 AM, Tatsuo Ishii wrote:
>> Ok, it seems impossible to do that by using any public interfaces
>> currently available in PostgreSQL 9.0. I will create a custom C
>> function to be distributed along with pgpool-II.
>
> Could you submit the function for 9.1? Thanks :-)
On 12 October 2010 23:28, Fujii Masao wrote:
> On Sat, Oct 9, 2010 at 10:04 AM, Brendan Jurd wrote:
>> I have just set up HS+SR for the first time, and for the most part,
>> the docs were excellent. The one exception for me was the discussion
>> of archive_cleanup_command. This is a pretty impo
On Thu, Oct 14, 2010 at 8:55 AM, Kevin Grittner
wrote:
> Robert Haas wrote:
>
>> Is this a JDBC patch or a PG patch? Are we tracking JDBC patches
>> using the CF app?
>
> If this were the only patch for setQueryTimeout in front of us I
> probably wouldn't have suggested that, but this thread star
I wrote:
> I rather wonder if we don't want two separate
> execution-time node types anyway, since what Append does seems
> significantly different from Merge (and MergeAppend would be just a
> misnomer).
I've been working on this patch, and have gotten the executor side split
out as a new node ty
On Thu, Oct 14, 2010 at 11:34 AM, Tom Lane wrote:
> I wrote:
>> I rather wonder if we don't want two separate
>> execution-time node types anyway, since what Append does seems
>> significantly different from Merge (and MergeAppend would be just a
>> misnomer).
>
> I've been working on this patch,
On Thu, Oct 14, 2010 at 08:22:21AM -0400, Robert Haas wrote:
> On Thu, Oct 14, 2010 at 2:59 AM, Radosław Smogura
> wrote:
> > On Wed, 13 Oct 2010 21:01:06 -0400, Robert Haas
> > wrote:
> >> Is this a JDBC patch or a PG patch? Are we tracking JDBC patches
> >> using the CF app?
> >
> > It is JDBC
On Thu, Oct 14, 2010 at 10:02 AM, Andrew Geery wrote:
> I didn’t have much time to look at the code. The only thing I’ll
> mention is that there are a couple of XXX TODO items that should be
> cleared up.
[...]
> Since this patch actually makes inheritance behave in a more expected
> way, nothing
What new public interfaces do you think are needed for 9.1 in this
regard?
Cheers,
David.
On Thu, Oct 14, 2010 at 11:10:14AM +0900, Tatsuo Ishii wrote:
> Ok, it seems impossible to do that by using any public interfaces
> currently available in PostgreSQL 9.0. I will create a custom C
> function t
Robert Haas writes:
> On Thu, Oct 14, 2010 at 11:34 AM, Tom Lane wrote:
>> Anybody have a strong feeling about what to call these things?
>> At the moment I'm leaning to sticking with MergeAppend, but if we
>> decide to rename it it'd probably be better to do so before committing.
> I don't like
Excerpts from Dimitri Fontaine's message of mié oct 13 18:11:21 -0300 2010:
> I like both ideas. I'd like to propose that we get back to this part of
> the feature later, after the first patch is in. After all, the main goal
> is to support dump&restore of extensions. Let's do that first.
Okay.
Excerpts from Magnus Hagander's message of jue oct 14 02:30:36 -0300 2010:
> And I agree it's not very friendly in this specific case - I
> wonder if we should log it as "localhost (127.0.0.1) and "localhost
> (::1)" (and similar for any other case that returns more than one
> address).
+1
--
Á
David Boreham wrote:
>
> As far as I can see there is no pre-built pg_filedump binary for the
> PDGD yum repository (8.3.11 for RHEL5). Before I embark on building it
> from source I figured I'd ask here if I'm correct that there is no
> binary hidden somewhere in the packages.
[ CC to hacker
On 14 October 2010 16:42, Robert Haas wrote:
> In view of the fact that we are out of time for this CommitFest, ...
>
When is the official end of this commitfest?
I remember talk at the start, that the end would be postponed (by a
week?) due to time spent on the git migration. Is that still the c
Sure. I just lose comments. I'll live with that.
Actually, as part of this scheme, it would be nice if pg_settings had a
"comment" column, which would be optionally set with SET PERMANENT. Not
required, but nice to have.
If we had that, I suspect that a lot fewer people would want a
hand
On ons, 2010-10-13 at 19:15 -0400, Robert Haas wrote:
> What's the status of this patch?
I would appreciate some more review of the basic architecture.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/
On tor, 2010-10-14 at 07:30 +0200, Magnus Hagander wrote:
> And I agree it's not very friendly in this specific case - I
> wonder if we should log it as "localhost (127.0.0.1) and "localhost
> (::1)" (and similar for any other case that returns more than one
> address).
That looks good.
--
Sent
--On 14. Oktober 2010 11:42:27 -0400 Robert Haas
wrote:
I did a sanity make clean && make && make check before applying the
patch and all the tests passed. After applying the patch and doing
make clean && make && make check, I got a number of failures of the
form “FAILED (test process exit
Robert Haas wrote:
> 2010/9/27 Devrim G?ND?Z :
> > On Mon, 2010-09-27 at 09:40 -0400, Robert Haas wrote:
> >> > Actually, I don't see any reason why not to backpatch it.
> >>
> >> I was wondering if it would cause package management headaches for
> >> people who had already modified their postgresq
On Thu, Oct 14, 2010 at 12:44 PM, Dean Rasheed wrote:
> On 14 October 2010 16:42, Robert Haas wrote:
>> In view of the fact that we are out of time for this CommitFest, ...
>
> When is the official end of this commitfest?
> I remember talk at the start, that the end would be postponed (by a
> wee
2010/10/14 Bruce Momjian :
> Robert Haas wrote:
>> 2010/9/27 Devrim G?ND?Z :
>> > On Mon, 2010-09-27 at 09:40 -0400, Robert Haas wrote:
>> >> > Actually, I don't see any reason why not to backpatch it.
>> >>
>> >> I was wondering if it would cause package management headaches for
>> >> people who h
On Thu, Oct 14, 2010 at 12:41 PM, Bruce Momjian wrote:
> David Boreham wrote:
>>
>> As far as I can see there is no pre-built pg_filedump binary for the
>> PDGD yum repository (8.3.11 for RHEL5). Before I embark on building it
>> from source I figured I'd ask here if I'm correct that there is no
>
On Thu, Oct 14, 2010 at 10:37 AM, Hitoshi Harada wrote:
> I found PostgreSQL accepts UNION DISTINCT but documents don't mention it.
>
> http://www.postgresql.org/docs/9.0/static/sql-select.html#SQL-UNION
>
> select_statement UNION [ ALL ] select_statement
>
> UNION DISTINCT is nothing more than UN
Robert Haas wrote:
> 2010/10/14 Bruce Momjian :
> > Robert Haas wrote:
> >> 2010/9/27 Devrim G?ND?Z :
> >> > On Mon, 2010-09-27 at 09:40 -0400, Robert Haas wrote:
> >> >> > Actually, I don't see any reason why not to backpatch it.
> >> >>
> >> >> I was wondering if it would cause package management
On Thu, Oct 14, 2010 at 12:40 PM, Josh Berkus wrote:
>
>> Sure. I just lose comments. I'll live with that.
>
> Actually, as part of this scheme, it would be nice if pg_settings had a
> "comment" column, which would be optionally set with SET PERMANENT. Not
> required, but nice to have.
>
> If we
Robert Haas wrote:
Kevin Grittner wrote:
> I thought we had decided on the client-side approach, but maybe
> I'm confused. I don't have a position one way or the other, just
> trying to understand the state of the conversation.
Well, I've been pretty vocal on supporting a client-side solution
On Thu, Oct 14, 2010 at 9:50 AM, Tom Lane wrote:
> The fact is that you cannot know the active value anyway without
> checking, because what you did with SET PERMANENT might be overridden
> in various session-local ways. The proposal for hand-edited versus
> machine-edited files just adds one mor
We got an interesting documentation document left by Christian Freund
recently, in regards to
http://www.postgresql.org/docs/9.0/interactive/install-windows-full.html
; it says:
Regarding 16.1.3 - "perl mkvcbuild.pl"
In case you use a German version of VC change line 69 in "Solution.pm" to:
--On 14. Oktober 2010 10:02:12 -0400 Andrew Geery
wrote:
The first failure I get is in the inherit tests (tail of
/src/test/regress/results/inherit.out):
alter table a alter column aa type integer using bit_length(aa);
server closed the connection unexpectedly
This probably means t
On 14 October 2010 17:40, Bernd Helmle wrote:
>
>
> --On 14. Oktober 2010 11:42:27 -0400 Robert Haas
> wrote:
>
>>> I did a sanity make clean && make && make check before applying the
>>> patch and all the tests passed. After applying the patch and doing
>>> make clean && make && make check, I g
Agreed, committed and backpatched.
On Thu, 2010-10-14 at 14:11 +0900, Fujii Masao wrote:
> Hi,
>
> --
> if (recoveryTarget == RECOVERY_TARGET_XID)
> snprintf(buffer, sizeof(buffer),
>"%s%u\t%s\t%s transaction %u\n",
>
1 - 100 of 137 matches
Mail list logo
