quote-less quoting
:-)
Robert Treat
On Mon, 2003-09-15 at 02:38, Andrew Dunstan wrote:
- Original Message -
From: Tom Lane [EMAIL PROTECTED]
Hannu Krosing [EMAIL PROTECTED] writes:
Tom Lane kirjutas P, 14.09.2003 kell 18:58:
Those seem pretty unmemorable and content
to
implement it seems mysterious (the one good explanation I heard required
nested transactions). Personally I would love to see some work done on
this, I think it's a major lacking in the postgresql function support.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
without oids;
ALTER TABLE
= alter table test set without oids;
ALTER TABLE
= alter table test set without oids;
ALTER TABLE
I think popping a notice that the table is already without oids could be
helpful. for sure these types of messages should not be warnings though.
Robert Treat
--
Build
On Thu, 2003-09-04 at 21:14, Bruce Momjian wrote:
When I do '\h alter' in psql, the content scrolls off my screen.
i think you need a bigger screen
Should we be using the pager for \h output?
in 7.3.4 we do, let me check 7.4...seems to work, though I am on beta1
on this box.
Robert Treat
, I forget).
Yes, new for 7.4: log_min_error_statement.
Actually it is in 7.3 as well
7.4 does have some new options though, including log_min_messages (or is
that the same as server_min_messages in 7.3?), log_error_verbosity, and
log_min_duration_statement.
Robert Treat
--
Build
? I can't seem to recall the differentiator there either.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister
src/include/libpq/pqcomm.h.
Tom, just curious as to what your resistance is to this feature? ISTM
that making this admin modifiable doesn't hurt anyone and could be
helpful to some people.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
http://developer.postgresql.org/ftpsite/binary/v7.3.4/RPMS/
Robert Treat
On Thu, 2003-08-28 at 11:18, Marie G. Tuite wrote:
Same issue - are there rpms anywhere for 7.3.4?
Thanks.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Tom Lane
Sent
be a notice if
you've turned it on.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's
and accept them.
Really my previous email was simply to point out to anyone implementing
the truncate cascade that truncate currently doesn't care if there is
really any data in the dependent tables, just that there are dependent
tables.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware
IIRC the message at the end of install used to echo out the startup
command (pg_ctl or postmaster), but now it gives some nice information
on how to get help. Should the startup message be put back in? Seems
like it is the most likely thing someone who just installed would want
to know.
Robert
Newton
thanks Vadim,
Robert Treat
--
PostgreSQL :: The Enterprise Open Source Database
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
Strike that, the how to run message comes at the end of initdb, not
install... Maybe we need a message after install telling newbies like
myself to run initdb... :-P
Robert Treat
On Tue, 2003-08-12 at 09:58, Robert Treat wrote:
IIRC the message at the end of install used to echo out
/createdb/load schema/load data cycle provides for a
better unit test than the truncate data/load data cycle does, so while I
see this functionality as handy for development, I wouldn't use it for
unit testing.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
that in the test environment.
Truncate isn't transaction safe either, so that shouldn't be a problem.
Proper syntax for his feature would seem like:
truncate table [cascade|restrict] ?
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
syntax for his feature would seem like:
truncate table [cascade|restrict] ?
Agreed.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
constraint $1
21809=# select count(*) from exception_notice_map;
count
---
0
(1 row)
21809=#
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go
Hey Thierry,
I'm forwarding this on to the hackers group to see if we can get an
authoritative answer, as you don't want to rely on my fuzzy memory. :-)
Anyone know the scoop on this?
Robert Treat
-- Forwarded Message --
Subject: Re: [ANNOUNCE] PostgreSQL Weekly
gborg
project and note that, unless there is substantial development it will
most likely be dropped from 7.5, perhaps moved to it's own gborg
project.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast
On Fri, 2003-08-01 at 15:29, Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
On Fri, 2003-08-01 at 14:46, The Hermit Hacker wrote:
Is there anyone actually using rserv who would be adverse to my removing
it from the source tar ball?
I'm not actually using it, but I'd be adverse
Yes, it is a done deal. I'm in the process of updating the main web site
and the sourceforge site, hopefully I'll be done sometime this morning.
Robert Treat
On Tue, 2003-07-29 at 09:17, Andrew Dunstan wrote:
Is 7.3.4 a done deal now? If so, the front page of the Pg web site needs
-FAQ?
There nothing stopping you from submitting improved wording for the FAQ
if you think it would be helpful.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 9: the planner
?) but it could be a
start.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
before page 1000 could
open up enough space to move the overly large tuple?
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 8: explain analyze is your friend
?
It would be VERY nice to do that, and maybe even the table?
Should it be a GUC like log_timestamp that can be applied to all log
messages?
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6
in the declare statement, if that doesn't
work, post the whole code for the function.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL
the
message to my own inbox.
FWIW I have it. Please be aware that archives isn't updating as of now,
so it's quite likely that it go flummoxed before this patch was sent.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast
messages. I noticed one I sent
following up Chris K-L's post about a database not starting never made
it to the list. I checked with the direct recipients and they all
received it...
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end
?
as the person doing the legwork, do you see one location or the other as
a hindrance to getting the release done?
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 3: if posting/reading through Usenet
Once you folks are done going through the remaining list of patches, can
we get someone to send a rough list of new features in 7.4 sent over to
-advocacy? Please feel free to highlight any items that you think
warrant special notice from a technical standpoint. Thanks in advance,
Robert Treat
Seems like we should also allow for a windows specific distribution of libpq
as well.
Robert Treat
On Tuesday 24 June 2003 10:43 pm, Bruce Momjian wrote:
Added to TODO:
* Allow creation of a libpq-only tarball
On Wed, 25 Jun 2003 08:59:41 -0300 (ADT), Marc G. Fournier wrote:
On Wed, 25 Jun 2003, Robert Treat wrote:
Seems like we should also allow for a windows specific distribution of libpq
as well.
I thought that the win32 stuff was being included as part of the base
distribution? IF so
On Mon, 2003-06-23 at 21:36, The Hermit Hacker wrote:
On Mon, 23 Jun 2003, Robert Treat wrote:
The target-date-based approach we've taken in the last couple of
releases seems much more productive.
productive on a small scale; for sure. productive for large scale
features... well
others to help
out more since they can't get something new until foo is completed.
This would also prioritize said developers time on the large project
rather than other non-prioritized tasks, and it also helps to ensure a
killer feature for those who want such things,
Robert Treat
--
Build A Brighter
On Monday 23 June 2003 10:43 am, Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
Here's a sure to be wildly unpopular suggestion:
Make the deciding factor for the next release support of foo (foo can
be win32, pitr, replication, 2PC, whatever...).
We've done that before (see WAL
extension?
There really isn't for this release. Any talk of delay is just a thought
on general policy for future releases.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 8: explain analyze
we have
to follow the corporate mold. Still, I'd rather not get into that debate
yet since I don't want to let the win32 guys off the hook yet!
win32 for the next release! go guys go!
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end
On Fri, 2003-06-20 at 10:42, Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
On Fri, 2003-06-20 at 06:59, Justin Clift wrote:
The only thing that makes me wince is that we have a protocol change at
PostgreSQL 7.4 release instead of 8.0.
...which is why I'd advocate making
or bruce
in my patch submissions i don't expect them to bend to my whims, but as
someone who follows and participates in postgresql development
regardless of an marketing aspects, i don't mind pointing out
alternatives.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
on gborg,
or maybe hidden in contrib somewhere. I'd like a copy if you don't mind,
I currently use reindex regularly on my database but your script sounds
a little more informational.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end
features
causes trouble with postgresql development, but I don't see why a
release can't be based around waiting for feature x as long as feature x
is being actively worked on by trusted developers who have an endgame in
sight.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Justin,
can you add this to the release notes section on the sourceforge site if it's
not already there?
Robert Treat
On Saturday 14 June 2003 12:02 am, Justin Clift wrote:
Hi guys,
Although the Proof of Concept build works, it does have a few drawbacks:
+ Only works on English (US
in the past and might be a good way to
get your feet wet.
Once you get up and running be sure to come back and help us beta test!
:-)
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 5: Have
Can you send in a report for the supported platforms list?
http://developer.postgresql.org/docs/postgres/supported-platforms.html
Robert Treat
On Tue, 2003-06-10 at 13:16, Martin D. Weinberg wrote:
Hi folks,
We recently built a dual K8D-based Opteron box running Linux in 64-bit
mode (Debian
some of this information, but
clearly understand that users can always submit arbitrary sql to get the
same information, so you'd have to change the back end's security model
to really keep people from finding this kind of information out. I know
many of our users would welcome that change.
Robert
for the next few days btw which is why I'm chiming in)
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
somewhat
common names (max_fsm_relations and max_fsm_pages) or else it would really be
easy to overlook some settings.
Robert Treat
On Saturday 07 June 2003 12:33 pm, Bruce Momjian wrote:
I think people thought if you were doing SHOW ALL, you were looking for
a specific variable, so
of the postgresql.conf
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
If they have a letter to the editor or web forum, it might be worth
posting the change there in case others reading the article want to try
the compile.
Robert Treat
On Sat, 2003-05-31 at 11:56, Peter Eisentraut wrote:
A German computer magazine (c't 7/2003) tested the Intel C/C++ compiler
This message on the admin list has directions for recompiling the 7.3.3
SRPM on red hat 7.2
http://archives.postgresql.org/pgsql-admin/2003-05/msg00409.php
Robert Treat
On Thu, 2003-05-29 at 07:26, ow wrote:
RH7.3 is a supported distribution for at least 6 months. Any plans to add
Postgres
, not any
specific companies. Hopefully when I'm done I can post a thorough
review.
Robert Treat
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
See chapter 6.6.3. POSIX Regular Expressions in the Users Guide
Robert Treat
On Thu, 2003-03-13 at 20:27, Partho Bhowmick wrote:
Is the regular expression used by Postgres POSIX compliant?
Regards,
Partho
---(end of broadcast)---
TIP 3
with the fe/be protocol changes. If thats true, it seems to
me this makes the GUC method the most limiting.
Robert Treat
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL
position on this that we might as well worry
about whether it's going to be 7.4 or 8.0 once we hit feature freeze; by
then the whole discussion could be irrelevant.
Robert Treat
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ
support did, which
required most adminy apps to be worked over)
A protocol change however, would warrant a version number bump IMHO. I
would guess that by the time all of the protocol changes could be
completed, we'd have win32 or pitr, so it will hopefully be moot.
Robert Treat
On Thu, 2003-02-27 at 11:00, Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
Now that indexes are getting some reporting, my understanding is an
index would report fewer pages overall than it's associated table, but
those pages would be completely empty. However, given
On Saturday 15 February 2003 09:48 am, mlw wrote:
Robert Treat wrote:
Seems like some are saying one of the problems with the current system
is it doesn't follow FHS or LSB. If those are valid reasons to change
the system, it seems like a change which doesn't actually address those
concerns
On Thu, 2003-02-13 at 19:22, Adam Haberlach wrote:
On Thu, Feb 13, 2003 at 05:59:17PM -0500, Robert Treat wrote:
On Thu, 2003-02-13 at 15:08, mlw wrote:
Stephan Szabo wrote:
On Thu, 13 Feb 2003, mlw wrote:
Personally I think a postgresql installation is much more like an apache
enough mechanisms
for actually giving people the information they need to determine the
changes they need, a complete auto-tune seems premature.
Robert Treat
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org
you haven't done anything too wacky, you should be
able to drop your 7.2 database, reload the 7.2 schema, then load up the
7.3 data. As always, test this out before doing it on a production
system.
Robert Treat
---(end of broadcast)---
TIP 5: Have
directory when someone else
set up the system.
find / -name postgresql.conf -print
you now know where all of your configuration files are and where the
data for each of those servers is as well.
(Not I'm not against the idea...)
Robert Treat
---(end of broadcast
installation is much more like an apache
installation, which generally contains all of the files (data and
config) under /usr/local/apache. Maybe someone can dig more to see if
that system is more appropriate a comparison than something like bind.
Robert Treat
---(end
On Thu, 2003-02-13 at 14:28, Bruce Momjian wrote:
Robert Treat wrote:
On Thu, 2003-02-13 at 14:06, mlw wrote:
I will be resubmitting my patch for the 7.3.2 tree.
I'm no core developer, but surely this wont be included in the 7.3.x
branch. Any change needs to be made against
On Thu, 2003-02-13 at 14:43, Bruce Momjian wrote:
Robert Treat wrote:
On Thu, 2003-02-13 at 12:13, mlw wrote:
My patch only works on the PostgreSQL server code. No changes have been
made to the initialization scripts.
The patch declares three extra configuration file parameters
On Thu, 2003-02-13 at 14:51, mlw wrote:
Robert Treat wrote:
On Thu, 2003-02-13 at 12:13, mlw wrote:
My patch only works on the PostgreSQL server code. No changes have been
made to the initialization scripts.
The patch declares three extra configuration file parameters
on it.
Robert Treat
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
when building postgresql, as well
changeable via a command line option, any other places?
Robert Treat
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
servers these days (running linux as least) though out of the
box I might be more inclined to limit it to 64. If you do hit a file
descriptor problem, *you are hosed*.
Robert Treat
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ
is it for the rpm/package/deb/exe
maintainers to modify their supplied postgresql.conf settings when
building said distribution? AFAIK the minimum default SHHMAX setting on
Red Hat 8.0 is 32MB, seems like bumping shared buffers to work with that
amount would be acceptable inside the 8.0 rpm's.
Robert
that it may have been a better solution could still hold up.
Robert Treat
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
production grade or merely a
vast improvement over the cygwin developers version, well I bet the
windows folks would appreciate that. Even more so if someone runs those
tests against a linux box so that we have actual statistics to compare
against.
Robert Treat
---(end
I don't know if this is terribly helpful, but the message was around in
7.2.x, look at src/backend/access/heap/heapam.c around line 1808 (or
1823 in the 7.3.x code)
That said, I've not seen it before, perhaps you can expand upon what
your function is doing?
Robert Treat
On Mon, 2003-01-27 at 11
On Wed, 2003-01-22 at 14:23, Marc G. Fournier wrote:
If anyone has any 'last minute' issues they would like to see in either,
please speak now or forever hold your peace :)
Can someone post a changelog for these releases? Also what tags will
be created/used in CVS?
Robert Treat
/solutions of using md5 passwords inside
postgresql. this has tripped up a lot of people upgrading to 7.3
* possibly go into server resource issues and the pitfalls in giving
free form sql access to just anyone. (Think unconstrained join on all
tables in a database)
hth,
Robert Treat
On Mon, 2003-01
FUD to sling this way.
Robert Treat
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Have we decided it's really too difficult to remove all references to a
given sysid when the user is dropped? It seems like we're creating
multiple new problems in an effort to workaround one existing problem.
Robert Treat
On Fri, 2003-01-17 at 12:38, Bruce Momjian wrote:
Tom Lane wrote
On Fri, 2003-01-17 at 14:32, Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
Have we decided it's really too difficult to remove all references to a
given sysid when the user is dropped?
Getting at objects in other databases is considerably less practical
than anything we've
and columns easily. Now that we have that in 7.3,
it might be worth revisiting.
Robert Treat
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
.
Perhaps this means we need to put more focus in finding ways to get
other parts of the site mirrored.
Robert Treat
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
You have to do it in functions because some of the \ commands use
multiple queries and logic inside the C code.
Robert Treat
On Mon, 2003-01-13 at 16:42, Greg Copeland wrote:
Views or C-functions, I think the idea is excellent. It's the concept
that I really like.
Greg
On Mon, 2003
throwing things at me if I volunteered :-)
Robert Treat
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
.
Thats the approach we've taken with phppgadmin 3, and while it
complicates things it does have it's benefits.
Robert Treat
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
the edited query in the history would be more useful than
\e - the latter is only three key presses any how ;-)
Or if the query could be appended after the \e, it would only be a quick
double-up to get back to the \e.
Robert Treat
---(end of broadcast
, probably both. If there is a
downside then ipv4, since it much more likely to be the default on OS's
for the next release or two.
Robert Treat
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
be
enough if people are worried about me trashing things :-)
Robert Treat
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get
On Thu, 2002-12-19 at 12:58, Bruce Momjian wrote:
OK, what additional things need to be done for 7.3.1? As far as I know,
we have done everything.
Do we want to coordinate with Lamar or Oliver about having packages
ready to coincide with the release announcement?
Robert Treat
Is this going to be announced to a wider press audience? Has anyone gone
over the list of things to do when we release to make sure things like
the websites getting updated or perhaps getting rpm builds coordinated
has been done?
Robert Treat
On Wed, 2002-12-18 at 09:18, Marc G. Fournier wrote
On Wed, 2002-12-18 at 09:51, Marc G. Fournier wrote:
On Wed, 18 Dec 2002, Robert Treat wrote:
Is this going to be announced to a wider press audience? Has anyone gone
over the list of things to do when we release to make sure things like
the websites getting updated or perhaps getting rpm
if it is done lets make sure we add
documentation to point out that we aren't compliant on this issue.
Robert Treat
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL
go in this scenario though, so a general software
tuning section does seem appropriate. Do you see a 3.8 Tuning the Server
(Hardware) section as well?
Robert Treat
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send
that until you get a decent website your
not going to be taken seriously than anything else, by far. While I'm
hoping that's not entirely true, I do agree that until we get a coordinated and
open web development process the advocacy group is going to have a much
harder go of it.
Robert Treat
excessive.
For larger or more complex tables, the output of VACUUM ANALYZE must be used.
snip
again, great work Philip.
Robert Treat
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs
.
Can we not just have vacuum of a database return a total # of pages
modified and relations modified, and then report suggested free space map
settings? Even this little bit would be a step in the right direction.
Robert Treat
---(end of broadcast
guys didn't just tell them ok we'll port the service to oracle/solaris
for you, but it's going to cost you at least twice what it does now, if not
three times. Oh, and you won't see any better performance.
Robert Treat
---(end of broadcast)---
TIP 3
On Saturday 07 December 2002 11:10 pm, Vince Vielhaber wrote:
On 5 Dec 2002, Robert Treat wrote:
On Thu, 2002-12-05 at 03:28, Dave Page wrote:
www is a closed group consisting of a few of us who actually do the
work on the sites.
This is one of the primary reasons the sites are so
list you were SUPPOSED to join.
fiefdoms!!
Robert Treat
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
of those) and the folks maintaining those lists seem to
be against letting anyone into their fiefdoms.
Robert Treat
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister
On Thu, 05 Dec 2002 21:26:13 -0500, Philip Warner wrote:
At 12:12 AM 5/12/2002 -0500, Robert Treat wrote:
I am happy with increasing market share so long a development is not
distorted or current users inconvenienced. We have seen the latter with
the misplaced announcements.
It seems to me
done. Read committed transactions seem broken without
this ability.
Robert Treat
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can
think the
causality works *both* ways.
Aren't most development efforts made simply to gain market share? After
all, I don't think we added schema support to get *less* people to use
postgresql.
Robert Treat
---(end of broadcast)---
TIP 3: if posting
701 - 800 of 828 matches
Mail list logo
