David E. Wheeler wrote:
On Jun 15, 2010, at 3:23 PM, Robert Haas wrote:
I think this project is a great idea, and I think as a community we
ought to be behind it 100%.
However, I do wonder what happened to the original name, which IIRC
was PGAN. That seems easier to pronounce, remember, ...
Hi,
GetOldestWALSendPointer() is commented out in the source code
with NOT_USED block, but is still declared in the header file.
Should we remove the function prototype from walsender.h ?
[walsender.h]
extern XLogRecPtr GetOldestWALSendPointer(void);
Regards,
---
Takahiro Itagaki
NTT Open So
On Tue, 2010-06-15 at 16:12 -0400, Bruce Momjian wrote:
> This was just posted to announce.
I notice you mention that this was just posted to the ANNOUNCE list.
Who is it that moderates the announce list?
The postings made by David Fetter on 13 June and postings by David
Wheeler on 15 June were
On Wed, Jun 16, 2010 at 7:03 AM, Stefan Kaltenbrunner
wrote:
> David E. Wheeler wrote:
>>
>> On Jun 15, 2010, at 3:23 PM, Robert Haas wrote:
>>
>>> I think this project is a great idea, and I think as a community we
>>> ought to be behind it 100%.
>>>
>>> However, I do wonder what happened to the
On Jun 16, 2010, at 8:47 , Amir Abdollahi wrote:
> I want to add a new backend process to postgres, to include my own auditing
> modules.
> How can i do that, also how can i signal it after!
The existing auxiliary processes (in 8.4) and their entry points are
autovacuum (autovacuum.c, AutoVacLau
On Wed, Jun 16, 2010 at 12:27, Simon Riggs wrote:
> On Tue, 2010-06-15 at 16:12 -0400, Bruce Momjian wrote:
>
>> This was just posted to announce.
>
> I notice you mention that this was just posted to the ANNOUNCE list.
>
> Who is it that moderates the announce list?
I can't answer this part, jus
On Wed, Jun 16, 2010 at 5:31 AM, Bernd Helmle wrote:
>
>
> --On 15. Juni 2010 20:51:21 -0700 Selena Deckelmann
> wrote:
>
>> Confirmed that this tests fine against commit id
>> 0dca7d2f70872a242d4430c4c3aa01ba8dbd4a8c
>>
>> I also wrote a little test script and verified that it throws an error
>>
Tim Bunce wrote:
If the "feature" is not any use should we rip it out? We pretty much
included it because you said it was what you needed for the
profiler.
Yes, it can go.
Done.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chang
--On 15. Juni 2010 20:51:21 -0700 Selena Deckelmann
wrote:
Confirmed that this tests fine against commit id
0dca7d2f70872a242d4430c4c3aa01ba8dbd4a8c
I also wrote a little test script and verified that it throws an error
when I try to remove a constraint from the parent table.
Thanks for
Takahiro Itagaki writes:
> GetOldestWALSendPointer() is commented out in the source code
> with NOT_USED block, but is still declared in the header file.
> Should we remove the function prototype from walsender.h ?
Yes, that's our usual convention.
regards, tom lane
--
On Wed, 2010-06-16 at 09:03 +0200, Stefan Kaltenbrunner wrote:
> David E. Wheeler wrote:
> > On Jun 15, 2010, at 3:23 PM, Robert Haas wrote:
> >
> >> I think this project is a great idea, and I think as a community we
> >> ought to be behind it 100%.
> >>
> >> However, I do wonder what happened to
David E. Wheeler wrote:
> Honestly, I didn't realize anyone was attached to ?PGAN.?
>
> Frankly, I blame whoever named PostgreSQL itself and came up with the
> short version, ?PG.? Nothing but pigs out of that.
I finally understand how pig-squeal is a short-form of PostgreSQL
(PG-SQL). :-O Yet
Joshua D. Drake wrote:
> On Wed, 2010-06-16 at 09:03 +0200, Stefan Kaltenbrunner wrote:
> > David E. Wheeler wrote:
> > > On Jun 15, 2010, at 3:23 PM, Robert Haas wrote:
> > >
> > >> I think this project is a great idea, and I think as a community we
> > >> ought to be behind it 100%.
> > >>
> > >
KaiGai,
* KaiGai Kohei (kai...@ak.jp.nec.com) wrote:
> On the other hand, a security feature have to identify the client and
> assign an appropriate set of privileges on the session prior to it being
> available for users.
[...]
> However, here is no hooks available for the purpose.
I believe we
Why is there significant delay on important posts, yet some posts go
almost straight though? Every time I use Announce my posts are delayed
for about 4-5 days.
Why do some posts jump the queue, appearing to imply the moderator is
being selective in releasing some, yet not others?
Do we need so
On Wed, 2010-06-16 at 13:22 -0400, Bruce Momjian wrote:
> > I actually like PGXN. PGXN is marketable. Yeah that may not be what
> > -hackers are after but if I stand up in front of a Fortune 500 company
> > and say, "We have PGXN" it sounds a heck of a lot better that PGAN.
>
> I think the attrac
On Jun 14, 2010, at 2:22 , Greg Smith wrote:
> Florian Pflug wrote:
>> To be able to asses the performance characteristics of the different
>> wal-related options, I patched pgbench to show the average latency of each
>> individual statement. The idea is to be able to compare the latency of the
Running pg_upgrade against an unmodified (the output of initdb) cluster
on AIX is giving me "pg_alloc: Out of memory" errors.
On some non-linux platforms (including AIX) malloc(0) returns 0.
with the attached patch to pg_upgrade I am now able to get pg_upgrade to
convert an 8.3 database con
On Wed, 2010-06-16 at 13:05 +0200, Magnus Hagander wrote:
> On Wed, Jun 16, 2010 at 12:27, Simon Riggs wrote:
> > On Tue, 2010-06-15 at 16:12 -0400, Bruce Momjian wrote:
> >
> >> This was just posted to announce.
> >
> > I notice you mention that this was just posted to the ANNOUNCE list.
> >
> >
2010/6/16 David E. Wheeler :
> On Jun 15, 2010, at 3:23 PM, Robert Haas wrote:
>
>> I think this project is a great idea, and I think as a community we
>> ought to be behind it 100%.
>>
>> However, I do wonder what happened to the original name, which IIRC
>> was PGAN. That seems easier to pronoun
Steve Singer wrote:
>
> Running pg_upgrade against an unmodified (the output of initdb) cluster
> on AIX is giving me "pg_alloc: Out of memory" errors.
>
> On some non-linux platforms (including AIX) malloc(0) returns 0.
>
> with the attached patch to pg_upgrade I am now able to get pg_upgrade
On Mon, Jun 14, 2010 at 7:55 AM, Simon Riggs wrote:
>> But that change would cause the problem that Robert pointed out.
>> http://archives.postgresql.org/pgsql-hackers/2010-06/msg00670.php
>
> Presumably this means that if synchronous_commit = off on primary that
> SR in 9.0 will no longer work co
On Wed, 2010-06-16 at 15:47 -0400, Robert Haas wrote:
> So, obviously at this point my slave database is corrupted beyond
> repair due to nothing more than an unexpected crash on the master.
> That's bad. What is worse is that the system only detected the
> corruption because the slave had crosse
Robert Haas wrote:
> So, obviously at this point my slave database is corrupted beyond
> repair due to nothing more than an unexpected crash on the master.
Certainly that's true for resuming replication. From your
description it sounds as though the slave would be usable for
purposes of takin
On 06/16/2010 09:47 PM, Robert Haas wrote:
On Mon, Jun 14, 2010 at 7:55 AM, Simon Riggs wrote:
But that change would cause the problem that Robert pointed out.
http://archives.postgresql.org/pgsql-hackers/2010-06/msg00670.php
Presumably this means that if synchronous_commit = off on primary t
Robert Haas wrote:
> I don't know what to do about this
This probably is out of the question for 9.0 based on scale of
change, and maybe forever based on the impact of WAL volume, but --
if we logged "before" images along with the "after", we could undo
the work of the "over-eager" transaction
Stefan Kaltenbrunner wrote:
> well this is likely caused by the OS not noticing that the
> connections went away (linux has really long timeouts here) -
> maybe we should unconditionally enable keepalive on systems that
> support that for replication connections (if that is possible in
> the cur
> The first problem I noticed is that the slave never seems to realize
> that the master has gone away. Every time I crashed the master, I had
> to kill the wal receiver process on the slave to get it to reconnect;
> otherwise it just sat there waiting, either forever or at least for
> longer tha
On Wed, Jun 16, 2010 at 4:00 PM, Kevin Grittner
wrote:
> Robert Haas wrote:
>> So, obviously at this point my slave database is corrupted beyond
>> repair due to nothing more than an unexpected crash on the master.
>
> Certainly that's true for resuming replication. From your
> description it so
On Wed, Jun 16, 2010 at 4:14 PM, Josh Berkus wrote:
>> The first problem I noticed is that the slave never seems to realize
>> that the master has gone away. Every time I crashed the master, I had
>> to kill the wal receiver process on the slave to get it to reconnect;
>> otherwise it just sat th
Robert Haas wrote:
> Kevin Grittner wrote:
>> Robert Haas wrote:
>>> So, obviously at this point my slave database is corrupted
>>> beyond repair due to nothing more than an unexpected crash on
>>> the master.
>>
>> Certainly that's true for resuming replication. From your
>> description it sou
On Wed, Jun 16, 2010 at 22:26, Robert Haas wrote:
>>> and this just
>>> makes it more likely. After the most recent crash, the master thought
>>> pg_current_xlog_location() was 1/86CD4000; the slave thought
>>> pg_last_xlog_receive_location() was 1/8733C000. After reconnecting to
>>> the master,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Haas wrote:
>
> The first problem I noticed is that the slave never seems to realize
> that the master has gone away. Every time I crashed the master, I had
> to kill the wal receiver process on the slave to get it to reconnect;
> otherwise i
Robert Haas writes:
> The first problem I noticed is that the slave never seems to realize
> that the master has gone away. Every time I crashed the master, I had
> to kill the wal receiver process on the slave to get it to reconnect;
> otherwise it just sat there waiting, either forever or at le
Hello,
I want to add a new backend process to postgres, to include my own auditing
modules.
How can i do that, also how can i signal it after!
Sorry if this is very general question!
I didn't find any source to learn these things in postgres.
thanks in advance
On Wed, 2010-06-16 at 10:34 -0700, Josh Berkus wrote:
> > Why is there significant delay on important posts, yet some posts go
> > almost straight though? Every time I use Announce my posts are delayed
> > for about 4-5 days.
> >
> > Why do some posts jump the queue, appearing to imply the moderato
> And me, and devrim and a number of others.
Hmmm. Yet nothing seems to get approved unless I personal e-mail Marc.
Why?
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.
On 6/16/10 1:26 PM, Robert Haas wrote:
> Similarly with synchronous_commit=off, I believe
> that the next checkpoint will still fsync WAL, but the lag might be
> long.
That's not a showstopper. Just tell people that having synch_commit=off
on the master might increase the lag to the slave, and le
> On Wed, 2010-06-16 at 10:34 -0700, Josh Berkus wrote:
> > > Why is there significant delay on important posts, yet some posts go
> > > almost straight though? Every time I use Announce my posts are delayed
> > > for about 4-5 days.
> > >
> > > Why do some posts jump the queue, appearing to imply
I don't moderate -announce.
--
Devrim GÜNDÜZ
PostgreSQL DBA @ Akinon/Markafoni, Red Hat Certified Engineer
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz
17.Haz.2010 tarihinde 00:58 saatinde, "Joshua D. Drake"
The real problem here is that we're sending records to the slave which
might cease to exist on the master if it unexpectedly reboots. I
believe that what we need to do is make sure that the master only
sends WAL it has already fsync'd
How about this :
- pg records somewhere the xlog position
On Wed, 2010-06-16 at 15:01 -0700, Josh Berkus wrote:
> > And me, and devrim and a number of others.
>
> Hmmm. Yet nothing seems to get approved unless I personal e-mail Marc.
> Why?
I approved stuff today and yesterday. I didn't the week before because I
was in Chicago. I also normally don't m
On Thu, 2010-06-17 at 01:17 +0300, Devrim GUNDUZ wrote:
> I don't moderate -announce.
Sorry. I thought you did.
JD
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
--
Sent via
On Wed, Jun 16, 2010 at 9:56 PM, Tom Lane wrote:
> Robert Haas writes:
>> The first problem I noticed is that the slave never seems to realize
>> that the master has gone away. Every time I crashed the master, I had
>> to kill the wal receiver process on the slave to get it to reconnect;
>> othe
>> Hmmm. Yet nothing seems to get approved unless I personal e-mail Marc.
>> Why?
>
> I approved stuff today and yesterday. I didn't the week before because I
> was in Chicago. I also normally don't moderate on the weekends. I was
> the one that approved the PGXN email for example.
This week i
On Wed, 2010-06-16 at 16:08 -0700, Josh Berkus wrote:
> >> Hmmm. Yet nothing seems to get approved unless I personal e-mail Marc.
> >> Why?
> >
> > I approved stuff today and yesterday. I didn't the week before because I
> > was in Chicago. I also normally don't moderate on the weekends. I was
>
Greg Stark wrote:
> TCP keepalives are for detecting broken network connections
Yeah. That seems like what we have here. If you shoot the OS in
the head, the network connection is broken rather abruptly, without
the normal packets exchanged to close the TCP connection. It sounds
like it beh
"Kevin Grittner" wrote:
> It sounds like it behaves just fine except for not detecting a
> broken connection.
Of course I meant in terms of the slave's attempts at retrieving
more WAL, not in terms of it applying a second time line. TCP
keepalive timeouts don't help with that part of it, just
On Tue, Jun 15, 2010 at 10:55 PM, David E. Wheeler wrote:
> On Jun 15, 2010, at 6:58 PM, Robert Haas wrote:
>
>> Well, the idea is it's like logical-and - give me only those keys that
>> appear on both sides...
>
> Yeah, but => doesn't return the keys, -> does. => returns an hstore.
>
>> If there
On Thu, Jun 17, 2010 at 12:22 AM, Kevin Grittner
wrote:
> "Kevin Grittner" wrote:
>
>> It sounds like it behaves just fine except for not detecting a
>> broken connection.
>
> Of course I meant in terms of the slave's attempts at retrieving
> more WAL, not in terms of it applying a second time li
(2010/06/16 21:37), Stephen Frost wrote:
> KaiGai,
>
> * KaiGai Kohei (kai...@ak.jp.nec.com) wrote:
>> On the other hand, a security feature have to identify the client and
>> assign an appropriate set of privileges on the session prior to it being
>> available for users.
> [...]
>> However, here
On Jun 16, 2010, at 4:24 PM, Robert Haas wrote:
>> Put me down for +>.
>
> Since there are no other votes for that option (or, indeed, any other
> option), I'm going to go with my original instinct and change hstore
> => text[] to hstore & text[]. Patch to do that is attached.
Damn. My other ar
On Thu, Jun 17, 2010 at 12:16 AM, Kevin Grittner
wrote:
> Greg Stark wrote:
>
>> TCP keepalives are for detecting broken network connections
>
> Yeah. That seems like what we have here. If you shoot the OS in
> the head, the network connection is broken rather abruptly, without
> the normal pac
Robert Haas writes:
> Since there are no other votes for that option (or, indeed, any other
> option), I'm going to go with my original instinct and change hstore
> => text[] to hstore & text[]. Patch to do that is attached.
Um ... wait a minute. What happened to backwards compatibility?
I thou
On Jun 16, 2010, at 4:53 PM, Tom Lane wrote:
> Um ... wait a minute. What happened to backwards compatibility?
> I thought the idea was to deprecate => for a release or so, not kill it
> on the spot.
hstore => text[] is new in 9.0.
David
--
Sent via pgsql-hackers mailing list (pgsql-hackers@
"David E. Wheeler" writes:
> On Jun 16, 2010, at 4:53 PM, Tom Lane wrote:
>> Um ... wait a minute. What happened to backwards compatibility?
>> I thought the idea was to deprecate => for a release or so, not kill it
>> on the spot.
> hstore => text[] is new in 9.0.
Wup, sorry, I read this as be
I have not been able to find any comments or discussion on this patch.
Contents and Purpose:
This patch removes duplicate code in opclasscmds.c. It removes the
duplicate code from DefineOpFamily by calling CreateOpFamily.
No new regression test or documentation are included wi
On Tue, Jun 15, 2010 at 4:22 AM, Fujii Masao wrote:
> On Tue, Jun 15, 2010 at 2:41 PM, Heikki Linnakangas
> wrote:
>> On 15/06/10 08:23, Fujii Masao wrote:
>>>
>>> On Thu, Jun 10, 2010 at 11:06 PM, Tom Lane wrote:
I'm not sure if it's worth the trouble, or even a particularly smart
>>>
On Wed, Jun 9, 2010 at 8:01 PM, Tom Lane wrote:
> Simon Riggs writes:
>> On Thu, 2010-06-03 at 19:02 -0400, Tom Lane wrote:
>>> I decided there wasn't time to get anything useful done on it before the
>>> beta2 deadline (which is, more or less, right now). I will take another
>>> look over the n
Hi David,
At a pdxpug gathering, we took a look at your patch to psql for
supporting multiple -f's and put together some feedback:
REVIEW: Patch: support multiple -f options
https://commitfest.postgresql.org/action/patch_view?id=286
==Submission review==
Is the patch in context diff format?
I tried to implement a modular se-pgsql as proof-of-concept, using the DML
permission check hook which was proposed by Robert Haas.
At first, please build and install the latest PostgreSQL with this
patch to add a hook on DML permission checks.
http://archives.postgresql.org/pgsql-hackers/2010-0
On Thu, Jun 17, 2010 at 5:26 AM, Robert Haas wrote:
> On Wed, Jun 16, 2010 at 4:14 PM, Josh Berkus wrote:
>>> The first problem I noticed is that the slave never seems to realize
>>> that the master has gone away. Every time I crashed the master, I had
>>> to kill the wal receiver process on the
On 17/06/10 02:40, Greg Stark wrote:
On Thu, Jun 17, 2010 at 12:16 AM, Kevin Grittner
wrote:
Greg Stark wrote:
TCP keepalives are for detecting broken network connections
Yeah. That seems like what we have here. If you shoot the OS in
the head, the network connection is broken rather ab
On Wed, Jun 16, 2010 at 12:24 PM, Takahiro Itagaki
wrote:
>
> Fujii Masao wrote:
>
>> This is because pg_archivecleanup puts the line break "\n" in the head of
>> debug message. Why should we do so?
>>
>> ---
>> if (debug)
>> fprintf(stderr, "\n%s: removing \"%s\"", prog
Currently, the JSON datatype (repository:
http://git.postgresql.org/gitweb?p=json-datatype.git;a=summary ) is
implemented somewhat like a specialization of TEXT, like XML is. I'm
beginning to question if this is the right way to go. This doesn't
concern whether the JSON datatype should retain the
On Wed, 16 Jun 2010, Josh Berkus wrote:
Why is there significant delay on important posts, yet some posts go
almost straight though? Every time I use Announce my posts are delayed
for about 4-5 days.
Why do some posts jump the queue, appearing to imply the moderator is
being selective in rele
On Thu, 17 Jun 2010, Tatsuo Ishii wrote:
On Wed, 2010-06-16 at 10:34 -0700, Josh Berkus wrote:
Why is there significant delay on important posts, yet some posts go
almost straight though? Every time I use Announce my posts are delayed
for about 4-5 days.
Why do some posts jump the queue, appea
Hi,
We should make trace_recovery_messages available only when
the WAL_DEBUG macro was defined? Currently it's always
available, so the standby seems to call elog() too frequently.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via p
> >> On Wed, 2010-06-16 at 10:34 -0700, Josh Berkus wrote:
> Why is there significant delay on important posts, yet some posts go
> almost straight though? Every time I use Announce my posts are delayed
> for about 4-5 days.
>
> Why do some posts jump the queue, appearing t
On Mon, Jan 18, 2010 at 3:55 AM, Takahiro Itagaki
wrote:
>
> Robert Haas wrote:
>
>> A couple of preliminary comments on this:
>
> Thanks.
> The attached is rebased on HEAD, with additional documentation.
>
This one, doesn't apply to head anymore... please update
--
Jaime Casanova www.
70 matches
Mail list logo
