[EMAIL PROTECTED] (Simon Riggs) writes:
> Comments welcome.
A minor change: I'd suggest creating these views as TEMP views, that
way they go away automatically.
diff -r1.1 create_tom_tables.sql
===
RCS file: get_data_for_tom.sql,v
re
[EMAIL PROTECTED] (Tom Lane) writes:
> Simon Riggs <[EMAIL PROTECTED]> writes:
>> I want to dump tables separately for performance reasons. There are
>> documented tests showing 100% gains using this method. There is no gain
>> adding this to pg_restore. There is a gain to be had - parallelising
>>
POSTGRESQL BUG REPORT TEMPLATE
Your name : Chris Campbell
Your email address : [EMAIL
[EMAIL PROTECTED] (Neil Conway) writes:
> Christopher Browne wrote:
>> One of our sysadmins did all the "configuring OS stuff" part; I don't
>> recall offhand if there was a need to twiddle something in order to
>> get it to have great gobs of shared memory.
>
> FWIW, the section on configuring ker
[EMAIL PROTECTED] (Peter Eisentraut) writes:
> Am Mittwoch, 30. August 2006 22:57 schrieb Chris Browne:
>> I also seem to recall, in past discussions about "library matters,"
>> that AIX is more sticky about requiring that libraries be named
>> expressly.
>
The change Tom made to contrib/sshinfo/Makefile to support Darwin,
adding in $(LIBS), fixed my problem with that contrib module on AIX.
I still need the following, on AIX:
===
RCS file: /projects/cvsroot/pgsql/contrib/dblink/Makefile
[EMAIL PROTECTED] (Tom Lane) writes:
> Chris Browne <[EMAIL PROTECTED]> writes:
>> I still need the following, on AIX:
>
>> -SHLIB_LINK = $(libpq)
>> +SHLIB_LINK = $(libpq) $(LIBS)
>
> No you don't --- see recent warthog complaint. We have to filter LIBS
&
[EMAIL PROTECTED] (Tom Lane) writes:
> Chris Browne <[EMAIL PROTECTED]> writes:
>> [EMAIL PROTECTED] (Tom Lane) writes:
>>> No you don't --- see recent warthog complaint. We have to filter LIBS
>>> down to just the minimum.
>
>> I'm at a loss, t
[EMAIL PROTECTED] (Bruce Momjian) writes:
> Great, I have added this to the bottom of the AIX FAQ. Thanks.
It seems to me that this also warrants an entry in the release notes.
I'd think that an entry in the Source Code Changes section,
immediately after the "Reduce libraries linked into the bac
t;"). This patch retains
this behavior for choosing to use the default service name, which
requires that NULL be passed in to DNSServiceRegister() as the
service name (rather than "" like the old API).
(4) I patched configure.in, but not configure. Is that right?
Thanks!
0.2 and earlier, I
guess we'll need to add a configure test for the presence of dlopen
()? Is that a check that should only be run on Darwin, or all platforms?
Thanks!
- Chris
dynloader.patch
Description: Binary data
---(end of broadcast)-
I noticed the following error in the chapter on ECPG...
[EMAIL PROTECTED]:pgsql-HEAD/doc/src/sgml> cvs diff -u ecpg.sgml
Index: ecpg.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v
retrieving revision 1.77
diff -c
[EMAIL PROTECTED] ("Heikki Linnakangas") writes:
> The original looks more correct to me. After the file has been run
> through the preprocessor, it becomes "preprocessed".
The other option I was thinking of was "postprocessed," because the .c
file comes *after* processing.
--
let name="cbbrowne"
reached greater maturity.
Any thoughts? Suggestions? I would also appreciate any advice on more
sophisticate ways to measure the performance impacts of a change like
this.
Thanks,
Chris Marcellino
Apple Computer, Inc.
posix_shmem.c
Description: Binary
ael, that is an interesting idea. That might be an avenue to
explore if there isn't a simpler way.
Thanks,
Chris Marcellino
On Feb 6, 2007, at 7:51 AM, Michael Paesold wrote:
Tom Lane wrote:
Chris Marcellino <[EMAIL PROTECTED]> writes:
To this end, I have "ported" the s
ice for confirming the existence of the other backend process.
Chris Marcellino
On Feb 6, 2007, at 10:32 AM, Alvaro Herrera wrote:
Chris Marcellino wrote:
Tom, that is a definitely valid point and thanks for the feedback. I
assume that the 'more modern' string segment naming gave the
Responses inline.
On Feb 6, 2007, at 7:05 PM, Takayuki Tsunakawa wrote:
From: "Chris Marcellino" <[EMAIL PROTECTED]>
To this end, I have "ported" the svsv_shmem.c layer to use the POSIX
calls (which are some ways more robust w.r.t reducing collision by
using str
Yes, as Tom pointed out. Sorry, I misread the autoconf file. I've
gotten quite used to Darwin == BSD.
I've added a note to my todo list to look into the posix semaphore
performance on the Darwin side.
--Chris
On Feb 6, 2007, at 8:32 PM, Takayuki Tsunakawa wrote:
Then, how about
king did you have in mind? Do you think this
might be worth me trying?
Thanks for your help,
Chris Marcellino
posix_shmem.c
Description: Binary data
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
darwin[015].*)
! USE_NAMED_POSIX_SEMAPHORES=1
! ;;
! *)
! USE_SYSV_SEMAPHORES=1
! ;;
! esac
Thanks,
Chris Marcellino
darwin
Description: Binary data
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
t the SysV semaphores use less memory (and no
fd's). Darwin can support about 85k SysV semaphores system-wide, so
it has no need for tuning in that respect, which is nice.
Chris Marcellino
On Feb 7, 2007, at 4:54 PM, Tom Lane wrote:
Chris Marcellino <[EMAIL PROTECTED]> writes:
I
awn from the SysV pool, so the SysV settings (SHMMAX, etc.) can be
set to their default values to recover the memory that was wired down
for the SysV pool.
I don't have access to any Linux machines to test this.
Thanks for your feedback,
Chris Marcellino
posix_shmem.c
Description: Bina
ry to
refactor this and return once again.
Thank you,
Chris Marcellino
On Feb 9, 2007, at 6:40 AM, Tom Lane wrote:
Chris Marcellino <[EMAIL PROTECTED]> writes:
Here is a new patch that uses the POSIX api's. It encodes the
canonical path (see 'man realpath') of the database
being silently
dropped when I attached this large of a file):
http://homepage.mac.com/cmarcellino/postgres-posix-shmem.tar
Please let me know if there is a better way to post this.
Thanks for your feedback,
Chris Marcellino
---(end of broadcast
On Feb 26, 2007, at 10:43 PM, Tom Lane wrote:
Chris Marcellino <[EMAIL PROTECTED]> writes:
The System V shared memory facilities provide a method to determine
who is attached to a shared memory segment.
This is used to prevent backends that were orphaned by crashed or
killed da
ndex
value that seems to be that, although I'm not certain.
This might make it easier to avoid the complexity of fitting the
filename in the segment name, and avoid the rename problem,
Thanks,
Chris Marcellino
On Feb 27, 2007, at 12:56 AM, Magnus Hagander wrote:
On Mon, Feb 26, 2007 at 09:
it is open? You could use the path of an arbitrary file in
that directory (like postgresql.conf) if this wasn't the case. We
would need to be sure it was already opened by postgres somehow
(which it should be).
Chris
On Feb 27, 2007, at 1:30 AM, Magnus Hagander wrote:
On Tue, Feb 27
,
Chris Marcellino
On Feb 27, 2007, at 1:40 AM, Magnus Hagander wrote:
On Tue, Feb 27, 2007 at 10:30:15AM +0100, Magnus Hagander wrote:
Does Windows have a method to get a unique ID number for a given
data
directory, or a token file in that directory? It would need to be
constant while the
n the
desired patches. An autoconf'ing of the patched configure.in file is,
of course, required.
I appreciate the feedback and consideration.
Thanks again,
Chris Marcellino
win32.patch
Description: Binary data
configure.in.patch
Description: Binary data
netbsd.patch
Description: B
o flesh out the
latter idea. Does anyone have any thoughts on whether this would be
worth trying? We have a strong need in our group to use POSIX shmem
and the more portable and robust it is, the better.
Thanks,
Chris
On Feb 28, 2007, at 9:24 AM, David Fetter wrote:
On Tue, Feb 27, 200
priate for mass distribution; I thought I would put
it out there for any feedback either way.
Thanks again,
Chris Marcellino
posix_shmem.c
Description: Binary data
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
still be reached on
some platforms if a ton of databases are opened simultaneously (i.e.
256 on Linux and Solaris, 100 on SCO Unix, 512 on HP-UX, 32 on Mac OS
X, unlimited on FreeBSD). This is the case without the patch anyhow.
Chris Marcellino
On Mar 3, 2007, at 9:09 AM, Joshua D. Drake
[EMAIL PROTECTED] (Neil Conway) writes:
> On Sun, 2007-13-05 at 22:06 -0400, Tom Lane wrote:
>> This fact is already documented in at least three places; do we really
>> need two more?
>
> I think we need to at least modify the documentation for the autovacuum
> GUC parameter, which currently state
[EMAIL PROTECTED] (Neil Conway) writes:
> On Wed, 2007-07-18 at 17:22 -0400, Alvaro Herrera wrote:
>> I wouldn't know how to look for other variadic functions using NULL
>> sentinels though.
>
> You would need something with more knowledge of C than "grep" has, at
> any rate. Perhaps you could teac
[EMAIL PROTECTED] ("Florian G. Pflug") writes:
> Pavan Deolasee wrote:
>> On 9/4/07, Florian G. Pflug <[EMAIL PROTECTED]> wrote:
>>> Hi
>>>
>>> Here is an updated patch, following the discussion.
>>> The patch can be found at: http://soc.phlo.org/lazyxidassign.v4.patch
>>> (I seems I still can't ge
IBM has addressed the socket address storage issue as of AIX 5.3
maintenance level 5300-03; the following patch adds documentation to
FAQ_AIX...
[EMAIL PROTECTED]:OXRS/sources/pgsql-HEAD/doc> cvs diff -u FAQ_AIX
Thursday 12:22:5
We haven't seen any agreement emerge as to what is causing AIX 5.3 ML3
to fail to successfully build the release candidates.
However, a patch has emerged (thanks, Seneca!) that does allow it to
work, and which I'd expect to be portable (better still!).
We are still actively pursuing why it breaks
[EMAIL PROTECTED] (Tom Lane) writes:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> I'm concerned that this still gives nondeterministic behavior.
>> There's no way to say, "I want readline, period" or "I want
>> libedit, period". I'd prefer simple --with-readline and
>> --with-libedit, giving
[EMAIL PROTECTED] (Simon Riggs) writes:
> On Sat, 2005-12-10 at 12:07 +, Simon Riggs wrote:
>> Following patch implements COPY ... FROM ... LOCK
>
> Patch now updated so that it includes an additional optimization of
> COPY, so that WAL will not be written in the transaction that created
> the
installing on anything
earlier than 10.3, my installer modifies /etc/rc. That way, when the
customer upgrades their server to 10.3.9 and the /etc/rc file is
overwritten, the /etc/sysctl.conf file is already in place.
Thanks!
- Chris
Referenced source code:
Mac OS X 10.4.4:
http://www.open
are correct). Only shmmax needs to be
multiples of the page size (at least, that's how I interpret the
Darwin code).
Thanks!
- Chris
---(end of broadcast)---
TIP 6: explain analyze is your friend
Some of this may have already made it in; it's not totally clear...
At any rate, here's a revision to CVS HEAD to reflect some changes by
myself and by Seneca Cunningham for the AIX FAQ. It touches on the
following issues:
1. memcpy pointer patch for dynahash.c
2. AIX memory management, which
[EMAIL PROTECTED]:/opt/OXRS/sources/pgsql-HEAD/doc$ cvs diff -u FAQ_AIX
Index: FAQ_AIX
===
RCS file: /projects/cvsroot/pgsql/doc/FAQ_AIX,v
retrieving revision 1.17
diff -c -u -r1.17 FAQ_AIX
cvs diff: conflicting specifications of outp
An article at WebProNews quoted from the PG docs as to the merits of
stored procedures. I have added a bit more material on their merits,
as well as making a few changes to improve the introductions to
PL/Perl and PL/Tcl.
Index: plperl.sgml
[EMAIL PROTECTED] (Christopher Kings-Lynne) writes:
>> The major downside is that somewhere between 9000 and 1
>> VALUES-targetlists produces "ERROR: stack depth limit
>> exceeded". Perhaps for the typical use-case this is sufficient
>> though.
>> I'm open to better ideas, comments, objections
the patch was his :)
Wondering if this makes a chance to get accepted...
Bye :-)
Chris.
diff -rc pgsql.original/doc/src/sgml/ref/psql-ref.sgml pgsql/doc/src/sgml/ref/psql-ref.sgml
*** pgsql.original/doc/src/sgml/ref/psql-ref.sgml Fri Jul 28 02:24:08 2006
--- pgsql/doc/src/sgml/ref/psql-ref.sgml
Here's a patch to add in the material on replication recently
discussed on pgsql.docs. I'm not thrilled that there were only a few
comments made; I'd be happy to see "slicing and dicing" to see this
made more useful.
Index: filelist.sgml
===
monic value whatsoever ... isn't there
> some other name we could use?
True :)
Since buffer commands all have a single char I wanted a single char one
too. The "c" for "cursor" was taken already, so i choose the "u" (second
char in "cursor"). If somebo
Replying to myself...
> Patch with fix against current CVS is attached.
Alvaro Herrera sent two fixes off-list: a typo and
at the end of SendQueryUsingCursor I sould COMMIT, not ROLLBACK.
So, one more version (6) that fixes these too is attached.
Bye, Chris.
PS: I'm keeping this on bo
> > Patch with fix against current CVS is attached.
Forgot the attachment... soory.
--
Chris Mair
http://www.1006.org
diff -rc pgsql.original/doc/src/sgml/ref/psql-ref.sgml pgsql/doc/src/sgml/ref/psql-ref.sgml
*** pgsql.original/doc/src/sgml/ref/psql-ref.sgml 2006-08-17 16:50:58.000
ith \pset I'd have different places where I'd need to figure
out whether to do the cursor thing and I was a bit reluctant to add
stuff to existing code paths. Also the other \pset options are somewhat
orthogonal to this one. Just my two EUR cents, of course... :)
Bye, Chris.
--
Chris
gt; > or some such.
\gc sounds like a good idea to me :)
(I must admit gc reminds me about 'garbage collector', which in a weired
way is related with what we're doing here... At least more related than
'Great Britain' ;)
> So add it as a modifyer to
an time I have been converted by the variable camp, and
I think the variable should change "\g" and ";" together, consistently.
If we find we can't live with the performance overhead of that
if(FETCH_COUNT), it is still not clear why we would be better
off moving i
I'm not at all sure that these are the right changes to apply; it
somewhat appears to me as though ecpg is supposed to be able to cope
with the omissions.
In any case, CVS HEAD is breaking on AIX 5.3 with GCC 4.1.1, and these
are the places where it's breaking.
Index: test1.pgc.in
===
for applying this,
psql is faster now.
Thanks to all people that helped with this (lots...:)
Bye, Chris.
--
Chris Mair
http://www.1006.org
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
I believe this change will apply equally to 7.4, 8.0, and CVS HEAD.
Index: FAQ_AIX
===
RCS file: /projects/cvsroot/pgsql/doc/FAQ_AIX,v
retrieving revision 1.11
diff -c -u -r1.11 FAQ_AIX
--- FAQ_AIX 12 Nov 2002 20:02:32 -
[EMAIL PROTECTED] ("Florian G. Pflug") writes:
> Chris Browne wrote:
>> Similarly, does it seem likely that Slony-I users would need to worry
>> about this?
> No.. it should have zero negative effects for Slony-I. In fact, it will
> be an advantage in some cases I th
[EMAIL PROTECTED] ("Marko Kreen") writes:
> Even the realistic code may be too much for general docs,
> but considering this is not a functionality covered
> by general SQL textbooks, I think it is worth having.
>
> I also put rendered pages up here:
>
> http://skytools.projects.postgresql.org/txi
As suggested to me by Ian Darwin <[EMAIL PROTECTED]>...
Index: doc/src/sgml/ref/pg_dump.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v
retrieving revision 1.97
diff -c -u -r1.97 pg_dump.sgml
--- doc/src/sgm
[EMAIL PROTECTED] ("Guillaume Smet") writes:
> On Dec 5, 2007 3:26 PM, Greg Sabino Mullane <[EMAIL PROTECTED]> wrote:
>> Agreed, this would be a nice 8.4 thing. But what about 8.3 and 8.2? Is
>> there a reason not to make this change? I know I've been lazy and not run
>> any absolute figures, but r
Yes, that is understandable. I'm not sure that there is a robust
portable solution that doesn't involve a major rearchitecture. I'm not
sure that would be worth the risk given the reward.
Thanks,
Chris
On Apr 2, 2008, at 8:50 AM, Bruce Momjian wrote:
The origin
current as the found WAL segment file's db changes, and prevents
recovery of that WAL file unless the rsync can be performed successfully.
(See attached file: pg_standby.c.diff)
Please consider incorporating this feature.
Chris
_
Christopher K. Jo
[EMAIL PROTECTED] (Bryce Nesbitt) writes:
> Alvaro Herrera wrote:
>> People [are] complaining here that we don't teach people here anyway, so
>> hopefully my comments were still useful :-)
>>
> Yes they are useful. As a new patcher, where should I look for coding
> standards? How about a little F
; > (See attached file: pg_standby.c.diff)
> >
> > This could be implemented by a "pass-through" restore_command, that
> > calls pg_standby, and does the custom action when pg_standby returns
> > successfully.
>
> Yes, that's the preferred route for mos
64 matches
Mail list logo
