ot;muti-master" is a frequently used term
and an eventual goal in core. Multi-primary doesn't seem to make much
sense.
--
Simon Riggshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-docs mailing lis
On 12 August 2016 at 18:54, Tom Lane wrote:
> Simon Riggs writes:
>> On 12 August 2016 at 16:23, Tom Lane wrote:
>>> I think "global" might have implications we don't want. How about
>>> adding ", based on a system-generated seed"?
>
>&
On 12 August 2016 at 16:23, Tom Lane wrote:
> Simon Riggs writes:
>> But now you mention it, I agree with you. Let's put it back to say
>> "sample" but also explain where that new sample comes from... my
>> attempt to explain this better is in square brack
On 12 August 2016 at 15:24, Tom Lane wrote:
> Simon Riggs writes:
>> On 11 August 2016 at 17:21, wrote:
>>> > If REPEATABLE is not given then a new random sample is selected for
>>> each
>>> query.
>>>
>>> the word "sampl
e
>
> > If REPEATABLE is not given then a new random sample is selected for each
> query.
>
> the word "sample" should be "seed". Of course it results
> in a new random
> sample as well, but IMHO this sentence is about what happens to the seed in
> cas
.
Either we should remove them all or add others back in. Which should we do?
--
Simon Riggshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes t
Couple of typos in src/backend/storage/ipc/dsm.c
Will apply if no objection, given vague possibility of change of meaning.
--
Simon Riggshttp://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training &
ormats, e.g. Slony, XL etc
If an automatic migration is possible do we need to change at all?
--
Simon Riggshttp://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
a pages have a 16-bit
> field available for future use with a data page checksum feature."
>
> Patch with correction suggestion attached.
Thanks Ian, well spotted.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Service
ed/lost, either.
Added separate comments for each point.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.post
option. I prefered
> tablespace_option because
> it's used also in psql's SQL help.
>
> Regards,
>
> --
> Fujii Masao
>
>
> --
> Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mai
011 etc.. if that really is interesting -
and if it really is then it should be listed as incompatibilities in
the release notes.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-docs mailing list (pgsql-docs@
On Mon, Oct 17, 2011 at 2:44 PM, Ray Stell wrote:
> On Sun, Oct 16, 2011 at 08:21:31PM +0100, Simon Riggs wrote:
>> On Fri, Oct 14, 2011 at 3:02 PM, Ray Stell wrote:
>>
>> > The tutorial here excludes an important issue:
>> > http://wiki.postgresql.org
itted and backpatched to 9.1
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
It seems to me we can do something a bit better than that.
It would be fairly straightforward to add some text to the end of the
ps message for long running DDL commands to say "phase 2" etc..
Or pg_stat_activity query text.
That way we would have some visibility into the progress of
nd "are detailed" instead of "was and were"
>
> I am pretty sure these books still exist.
I think both are correct, but you are right that those books still
exist and so it looks archaic and can be reworded.
--
Simon Riggs http://www.2ndQuadrant.com/
also that not all modules out there on the net will have been
updated either, so we must be able to discuss "extension-izing a
module". (??)
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-d
sort that out another day.
I will update the current code with some comments, so this doesn't
happen again. Will do this on Tuesday now, no time left here.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-docs mailing
e with 9.0, so it would be
> > nice to give those folks an accessible account of how
> > archive_cleanup_command is meant to be used.
>
> Yeah, if this is a material improvement in the usefulness of the HS
> docs, I think including it into 9.0.x isn't a bad idea.
D
efinition doesn't match the
actual code in CreateCheckPoint().
I've updated the docs to reflect how the code behaves.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-docs mailing list (pgsql-docs@postgr
On Fri, 2010-10-15 at 02:24 +1100, Brendan Jurd wrote:
> I'll drop this onto the next open commitfest. If it passes muster, it
> sure wouldn't hurt to backpatch it to 9.0.
Committed. Not sure there's anything there worth backpatching? There
aren't any doc bug
On Thu, 2010-06-24 at 18:22 -0400, Robert Haas wrote:
> On Thu, Jun 24, 2010 at 4:59 PM, Simon Riggs wrote:
> > On Thu, 2010-06-24 at 19:50 +, Robert Haas wrote:
> >> Log Message:
> >> ---
> >> Some copy-editing of the Hot Standby documentation.
&
On Thu, 2010-06-24 at 19:50 +, Robert Haas wrote:
> Log Message:
> ---
> Some copy-editing of the Hot Standby documentation.
>
> Thanks to Joshua Tolley for the review.
I rejected these changes. Please revoke.
--
Simon Riggs www.2ndQuadrant.com
--
Sent
.. FOR SHARE during Hot Standby, simply by
making it same as normal SELECT, without any ill effects.
--
Simon Riggs www.2ndQuadrant.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
27;s that many production-strength candidates that we
shouldn't mention them all. Right now, I see it as the only missing one
on the list.
BTW Bruce, "log shipping" isn't mentioned at all in that section, which
is strange since that's what's in 9.0.
--
Simon Rigg
ection pool, just like the other "background" processes.
>
> However, if this was somehow infeasible, it wouldn't be hard to
> document. That's all.
+1
--
Simon Riggs www.2ndQuadrant.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To ma
On Thu, 2010-03-25 at 12:15 +0200, Heikki Linnakangas wrote:
> (cc'ing docs list)
>
> Simon Riggs wrote:
> > The lack of docs begins to show a lack of coherent high-level design
> > here.
>
> Yeah, I think you're right. It's becoming hard to keep trac
limited scope of the answer this function provides.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Wed, 2008-11-26 at 22:14 +1300, Mark Kirkwood wrote:
> Simon Riggs wrote:
> >
> > You'll have problems stopping and starting standby, but the most
> > important change is that the process is not restartable. So if you
> run
> > it for a month and then cra
On Sun, 2008-09-07 at 08:31 -0400, Bruce Momjian wrote:
> Simon Riggs wrote:
> >
> > On Sat, 2008-09-06 at 21:31 -0400, Bruce Momjian wrote:
> > > Applied, and attached.
> >
> > Thanks.
> >
> > > > And for txid_visible_in_snapshot() co
t for a subtransaction xid
> > that was actually still in progress at the time of the snapshot".
>
> I think the cleaner solution is to throw an appropriate error if a
> subtransaction xid is used, rather than adding documentation.
Or maybe check subtrans for it, as it really sh
On Fri, 2008-09-05 at 16:14 +0100, Simon Riggs wrote:
> http://developer.postgresql.org/pgdocs/postgres/functions-info.html
>
> xip_list is described as
>
> "Active txids at the time of the snapshot... "
>
>
> This is incorrect. The xip_list is the list of t
or can the
snapshot data be used to monitor the number of transactions in progress.
Anyone disagree? If not, I'll patch.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make
sh, you'll need to re-run the whole month's
WAL data.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
The issue was raised because
pg_standby doesn't treat the file as optional, though recovery code
does.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Fri, 2008-05-09 at 10:28 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > Just had questions from a replication user about why the .backup file is
> > described as "can ordinarily be ignored" and is considered optional by
> > recovery
ain that
you can recover your data.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Could somebody re-add my email address to the pg_standby docs page?
It appears to have been removed while adding it to the main docs.
Thanks,
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your
On Fri, 2008-04-18 at 13:26 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > I'm trying to add a new ref/.sgml file, but I can't see which file needs
> > to change to allow that to be fully referenced.
>
> Example:
>
> $ gre
t.
Hit me with your cluesticks, please.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Wed, 2008-01-23 at 19:28 -0500, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > While compiling with PGXS, the OBJS line said
> > OBJS= modulename.so
>
> > By changing the OBJS line to this
> > OBJS= modulename.o
>
> >
then we should add a few
more lines of wisdom in this area.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
does not exist, which I think is
> what we want. This trigger function would not have to be modified when
> new tables are added.
I like your new trigger better than the old, but I am still
uncomfortable with recommending we use triggers with COPY for
performance reasons and we sho
On Sun, 2007-12-16 at 07:58 -0800, Joshua D. Drake wrote:
> Bruce Momjian wrote:
> > Simon Riggs wrote:
> >> Looks like we need some docs on all these new plugin APIs we've
> >> introduced in this release.
> >>
> >> - PL/pgSQL hooks
> >
based on the actual docs and thus we only need extended?)
>
> How about "smoothed?"
Agreed
"Smoothed" makes a lot of sense for me. We used to have a checkpoint
spike, now we don't.
Perhaps we should say something like "time extended checkpoints provide
smoother (transaction?) response times"
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Looks like we need some docs on all these new plugin APIs we've
introduced in this release.
- PL/pgSQL hooks
- planner hooks
- join order hooks
Thanks,
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
LIKE + COPY in
same transaction, then ALTER TABLE ... INHERITS to add the partition
onto the main table. That is now the fastest way in 8.3.
I'll leave it to y'all from here though.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadc
On Wed, 2007-11-28 at 17:36 -0500, Bruce Momjian wrote:
> Slightly modified patch attached and applied. Thanks.
Nice additions, thanks.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 4: Have
On Wed, 2007-11-28 at 10:12 -0300, Alvaro Herrera wrote:
> Simon Riggs wrote:
> >
> > A few docs changes, as mentioned.
> >
> > Comments?
>
> You forgot the patch :-)
No, just a very short patch. :-)
This patch is slightly longer...
--
Simon Riggs
2ndQua
A few docs changes, as mentioned.
Comments?
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
example ranking function to allow people
to write their own?
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Thu, 2007-11-08 at 10:10 +0100, Peter Eisentraut wrote:
> Am Donnerstag, 8. November 2007 schrieb Simon Riggs:
> > The main reason is that Slony is Copyrighted PGDG, so we own the code
> > and it is of course BSD licenced.
>
> Why is that a reason for mentioning it more
roach.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
On Tue, 2007-09-25 at 09:24 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > I'd like to reword this line in the Asynch commit docs:
> >"when transaction commit begins."
>
> I do not think your proposed rewording is better.
O
arameter can be set. The mode used
for
any one transaction depends on the value of
!synchronous_commit at the time of transaction
commit,
!so SET LOCAL can also be used.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(e
onverting the example to
> a block that will not change newlines:
>
> echo '\x
> SELECT * FROM foo;' | psql
>
> Is that what people want?
Well, it works, but IMHO its not as clear.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
ore.
So the -e is wrong, but the rest of the change was right. Guess we just
need to add a comment about "(you may need to use the -e option on echo
to get this to work on your OS)."
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
--
ROR: relation "foo" does not exist
Does this mean there are multiple forms of the echo command, or is this
example just wrong?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TI
On Tue, 2006-11-28 at 12:09 +0100, Peter Eisentraut wrote:
> Simon Riggs wrote:
> > I'm planning to
> > - add a new section to Performance Tips chapter called Dynamic
> > Tracing - rename the chapter Performance & Tuning.
> > - add some further intro stuff on
apter Performance & Tuning.
- add some further intro stuff on chapter header page
Comments?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
On Tue, 2006-10-24 at 15:33 -0700, Joshua D. Drake wrote:
> Simon Riggs wrote:
> > On Tue, 2006-10-24 at 15:13 -0700, Joshua D. Drake wrote:
> >
> >> If it were me, I would say that the replication option has to be
> >> specific to PostgreSQL (e.g; cjd
On Tue, 2006-10-24 at 15:13 -0700, Joshua D. Drake wrote:
> If it were me, I would say that the replication option has to be
> specific to PostgreSQL (e.g; cjdbc or synchronous jakarta pooling
> doesn't go in).
...and how do you define PostgreSQL exactly?
--
ly sort out the true differences in the above mix. But
that wouldn't help most people and almost everybody would find fault.
IMHO most people I've spoken to take "replication" to mean an HA
solution, so perhaps we should cover it in those terms.
--
Simon Riggs
En
h good solutions for open source PostgreSQL that it is easy
and straightforward to limit it to just that. New contributions welcome,
of course.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
On Fri, 2006-10-06 at 23:21 -0400, Bruce Momjian wrote:
> I have added links from the 8.2 release notes into our documentation.
> If people have additions/changes, please let me know.
Very cool.
--
Simon Riggs
EnterpriseDB http://www.enterprise
eas.
The DB2 manual does exactly that and is not any clearer as a result,
even if it is fully normalised.
If we did that we'd need to emphasise that VALUES is more of a clause
than a new command.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
--
On Sun, 2006-04-16 at 15:22 +0100, Simon Riggs wrote:
> On Sat, 2006-04-15 at 16:20 -0400, Bruce Momjian wrote:
> > Simon Riggs wrote:
> > > On Sat, 2006-04-15 at 12:24 -0400, Bruce Momjian wrote:
> > > > And if we can't provide one, should we supply an SQL fun
On Sat, 2006-04-15 at 16:20 -0400, Bruce Momjian wrote:
> Simon Riggs wrote:
> > On Sat, 2006-04-15 at 12:24 -0400, Bruce Momjian wrote:
> > > And if we can't provide one, should we supply an SQL function
> > > to return the current WAL name?
> >
> >
other things out.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
> continuously apply WAL files to a separate cluster in order to have a
> true hot standby system.
>
> Thoughts?
I'd include these as specific cases of the general workflow/checklist.
So, additions rather than refactoring. More words is better for most
people I think.
Best Regards, Si
ust say
'these terms are shorthand for ".." '
I'm not crazy about the terms but at least it is explicit and accurate.
It would also allow us to have a much longer description of all of the
implications and difficulties of each mode.
Best Regards, Simon Riggs
-
e". That would
then allow us to say:
"You can only take Online Backups while in WAL Archive Mode".
"If you ever wish to perform PITR, you must use WAL Archive Mode".
"If you backed-up in WAL Archive Mode, you can perform an Archive
Recovery".
Best Regards, Simon
On Tue, 2005-11-01 at 18:19 -0500, Neil Conway wrote:
> On Mon, 2005-31-10 at 22:41 +0000, Simon Riggs wrote:
> > I believe this is now complete and ready for application.
>
> Comments:
>
> - INSERT, UPDATE, etc. should be marked with , unless
> would be more appropr
nd of copy editing and then commit to CVS -- there
> will likely be room for additional improvements, so once it's in CVS
> anyone else who's interested can have at it.
Thanks guys.
Best Regards, Simon Riggs
---(end of broadcast)---
T
On Thu, 2005-10-20 at 17:59 -0400, Neil Conway wrote:
> On Thu, 2005-20-10 at 22:21 +0100, Simon Riggs wrote:
> > I like very much the split of that into two sections, but I think the
> > new chapter names are somewhat confusing.
>
> Yeah, I wasn't really sure abo
parameters" throughout, yet this is not mentioned in the
title. Also, the preset options section actually refers to settings that
are build-time parameters exposed at run-time, so perhaps the phrase
run-time is misleading.
Best Regards, Simon Riggs
---(e
On Sun, 2005-10-09 at 10:56 -0300, Alvaro Herrera wrote:
> Simon Riggs wrote:
> > I'm currently doing the docs for CE & Partitioning.
> >
> > The ddl.sgml chapter had a section on Inheritance. I'm expanding that
> > section and splitting it into two:
>
You will of course have another
chance to comment when I complete the patch.
Best Regards, Simon Riggs
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
ions. These relate to full_page_writes
and appropriate settings of wal_buffers to match.
Best Regards, Simon Riggs
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Sun, 2005-09-18 at 16:34 -0700, Josh Berkus wrote:
> Are there specific docs on CE anywhere in the PostgreSQL main
> documentation? I'd like to add a caution about that constraint
> specificity issue we uncovered.
Working on them now.
Best Regard
ut.
My patch was able to generate a different message by logging just before
the kill() is called. (Obviously, there isn't much "after" in this
circumstance).
Best Regards, Simon Riggs
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
oper is in the eye of the beholder; if you want it better, go for it.
Best Regards, Simon Riggs
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
reSQL tree)."
Surely this should refer to 8.0 also?
--
Best Regards, Simon Riggs
Index: README.xml2
===
RCS file: /projects/cvsroot/pgsql/contrib/xml2/README.xml2,v
retrieving revision 1.1
diff -d -c -r1.1 README.xml2
*** README.x
On Fri, 2004-11-26 at 22:34, Peter Eisentraut wrote:
> Simon Riggs wrote:
> > The sections Supported Features and Unsupported Features cover both
> > Mandatory (Core) and Optional features in the same section. It would
> > be better to separate these, just as the SQL st
able...XSLT?? other than maintaining two separate lists.
--
Best Regards, Simon Riggs
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
r those
> probably-not-conforming-but-just-maybe features, I suggest that we just go
> along with the above patch.
I've re-written the starting paragraphs, will post soon.
That doesnt conflict with your patch - which look like good detail.
--
Best Regards, Simon Riggs
nk the alpha index would be easier and more helpful
> to people doing fast lookups like Peter was looking for
> and lets the chapters stay in the nicely grouped format.
>
Agreed.
--
Best Regards, Simon Riggs
---(end of broadcast)---
TIP 6:
ere is a
> lot of stuff here, obviously. Wanna help?
Given how close we are to 8.0, we should just do a summary for the
release notes at least. I'll help with that... but not with the Full
Monty. :)
> On Sun, Nov 14, 2004 at 11:20:37PM +, Simon Riggs wrote:
> >
> >
IIRC there was some discussion earlier about including a (possibly
detailed) assessment of ANSI SQL-2003 conformance in the docs for 8.0.
My understanding was that there were people actually working on that.
Where are we with that? Anybody got news?
--
Best Regards, Simon Riggs
for and use the new access method. I'm both of those.
That gives us many of the benefits that Peter seeks, with minimal
change.
--
Best Regards, Simon Riggs
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
ome.
Many of these may not be appropriate for 8.0, but we can add these to the
TODO list for 8.1.
Best regards, Simon Riggs
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
On Mon, 2004-07-26 at 00:55, Bruce Momjian wrote:
> Simon Riggs wrote:
> > On Sun, 2004-07-25 at 05:25, Bruce Momjian wrote:
> > > I have completed the 7.5 release notes. You can view them in HTML on
> > > the developer web page. I have marked a few items with questi
er-supplied external program to
allow integration with external backup devices and related software.
> Do people want a big-picture paragraph at the top talking about the
> release? Some releases get them, some don't, but this one could if
> folks want it.
>
Ye
93 matches
Mail list logo
