On Wednesday 03 September 2008 09:17:54 Asko Oja wrote:
> On Wed, Sep 3, 2008 at 5:56 AM, Robert Treat
>
> <[EMAIL PROTECTED]>wrote:
> > On Tuesday 02 September 2008 17:21:12 Asko Oja wrote:
> > > On Tue, Sep 2, 2008 at 2:09 AM, Michael Nolan <[EMAIL PROTECTE
y, but there can be advantages to doing it using the pitr
tools, and I think in most cases it would be hard to argue it isn't safer.
As a counter example to theo's zfs based post, I posted a linux/lvm script
that can work as the basis of a simple snapshot backup tool, available at
h
e tpc-h allows for
changes to queries to support syntax variations between databases; I'm pretty
sure I could make suttle changes to "break" other databases as well.
Incidentally, I poked Mark Wong, who used to work at the OSDL (big linux
kernel hacking shop), and he noted he
gresql-8.1.html
http://people.planetpostgresql.org/xzilla/index.php?/archives/223-Measuring-database-restore-times.html
A little old, but might be helpful.
--
Robert Treat
http://www.omniti.com
Database: Scalability: Consulting:
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
o locking issues as well. Note, this can sometimes
apply to more narrow restore scenarios, but it isnt as cut and dried. (Ie,
with multiple database in a cluster, you dont want to disable it for all
databases, though it'd be nice to disable it for the one you're restoring)
--
Ro
h the pain of a dump/restore,
I'd suggest looking at upgrading to 8.3 during the process.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
tempted to just try copying the tables files directly between the two
directories if you can matchup the files on disk correctly. Otherwise you
might be forced to try and get some filesystem level tools going, but I'm not
sure how feasible that is on windows, especially on such an old v
e info, I've given at least one presentation on the topic, which
seems to be missing from the omniti site, but I've uploaded it to
slideshare...
http://www.slideshare.net/xzilla/postgresql-partitioning-pgcon-2007-presentation
HTH.
--
Robert Treat
http://www.omniti.com
Databa
ant to really move to
that version when you do the actual upgrade.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
e testing, and scripts that
> were to automate setup and manage the installation. It did not include
> support and maintenance.
Are you planning on hiring someone to do it, or are you going to do it
yourself, because the prices of the solution is completely orthogonal to
which is the bet
ad idea to
do begin; lock table t1 in access exclsuive mode; create temp table x as
select ... from t1; truncate t1; insert into t1 select * from x; create
unique index ui1 on t1(...); commit; this way you're now unique table will
be nice and compacted, and wont get any more duplicate
1st, so if you
did have something you wanted to get into 8.4, you have 2 weeks to make it
into the last commitfest; after that you're probably looking at 8.5.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-general mailing list (pgsql-
base, and restart normally.
--
Robert Treat
http://www.omniti.com
Database: Scalability: Consulting
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
t, isn't there a better way
> > to do this without shutting down postgres?
> >
> > Thanks in advandce.
>
> --
> Emanuel Calvo Franco
> Syscope Postgresql DBA
> BaPUG Member
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middlew
equired.
>
> What else do we need?
>
Is it possible to give the master/slave knowledge about each other?
--
Robert Treat
Conjecture: http://www.xzilla.net
Consulting: http://www.omniti.net
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes
On Monday 27 October 2008 12:12:18 Simon Riggs wrote:
> On Mon, 2008-10-27 at 11:42 -0400, Robert Treat wrote:
> > On Monday 20 October 2008 05:25:29 Simon Riggs wrote:
> > > I'm looking to implement the following functions for Hot Standby, to
> > > allow th
It would be good to know where and when his bottlenecks are... ie. i could see
him being i/o, memory, or cpu bottlenecked depending on where he is in the
restore process.
--
Robert Treat
Conjecture: http://www.xzilla.net
Consulting: http://www.omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
This assumes you're keeping the default table space on hdd, if you lose
the system catalogs, the right answer is "initdb"
--
Robert Treat
Conjecture: http://www.xzilla.net
Consulting: http://www.omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
."
>
> We really need a favorite Tom Lane quotes thread. Mine is (roughly):
>
http://archives.postgresql.org/pgsql-hackers/2006-04/msg00288.php
I remember after reading this post wondering whether Tom uses caffeinated
soap...
--
Robert Treat
Conjecture: http://www.xzilla.net
Con
ubset of the community. I had hopes that
it might follow autovacuums path and get moved into a contrib module and
possibly integrated into the backend some day, but I haven't seen much push
in that direction.
--
Robert Treat
Conjecture: http://www.xzilla.net
Consulting: http://www.omniti
our backup and then moving the missing logs manually. (This is
more/less fragile depending on exactly how you've set things up, but should
be doable)
--
Robert Treat
Conjecture: http://www.xzilla.net
Consulting: http://www.omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
d example (tracking pages across all databases),
but also things like work_mem need to account for all connections to all
databases when you think about how high you can set these. Don't forget some
of these settings (like work_mem) can be set per database using the ALTER
DATABASE command, j
ooking forward to another interesting year with GSoC,
and hoping you'll join in.
--
Robert Treat
Conjecture: http://www.xzilla.net
Consulting: http://www.omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
it seems less error prone, and you can
actually test the failover and lunch bits while the original server is
up and running.
Robert Treat
conjecture: xzilla.net
consulting: omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
lack of
> request (first request since 8.3.11...). You can build your own packages
> quite easily, though.
>
Hey Devrim, any chance you have published your rpm spec files you used
on the earlier 8.3 -id builds? I looked around and couldn't find one.
Robert Treat
conjecture: xz
2011/11/3 Devrim GÜNDÜZ :
> On Wed, 2011-11-02 at 13:16 -0400, Robert Treat wrote:
>> >
>>
>> Hey Devrim, any chance you have published your rpm spec files you used
>> on the earlier 8.3 -id builds? I looked around and couldn't find one.
>
> They were in t
rchitecture, but the two that have proven best in our
testing and production use (for ourselves and our clients) seem to be
Intel (mostly 320 series iirc), and Fusion-IO. I'd start with looking
at those.
Robert Treat
conjecture: xzilla.net
consulting: omniti.com
--
Sent via pgsql-gener
127.0.0.1/32 password
>
> The command I am running is:
> pg_dump -F c -v -X disable-triggers -U postgres -h 127.0.0.1 -p
> 5432 -f ./test.backup
>
Does pgadmin also connect via 127.0.0.1? What happens if you dump via
the local socket? Also, do you get an error for pg_dump,
, and when stuff fails because you lied to the
> system, you will probably never ever figure out or even know.
>
Agreed. I'd be more inclined to change londiste, or just ditch it for
something else that will recognize the unique index as a unique enough
identifier to enable replication. Th
If you are trying to kill one specific connection/backend, I'd
recommend using the pg_terminate_backend(pid_goes_here) function.
Robert Treat
conjecture: xzilla.net
consulting: omniti.com
On Wed, Nov 9, 2011 at 5:18 PM, Mike Blackwell wrote:
> The manual section on the postmaster pro
ostgresql.org/docs/9.1/interactive/release-8-4.html#AEN111313
http://www.postgresql.org/docs/9.1/interactive/release-8-3.html#AEN114593
Robert Treat
conjecture: xzilla.net
consulting: omniti.com
On Thu, Nov 17, 2011 at 8:14 PM, David Morton wrote:
> I've performed a very similar upgrade
s that can be shipped off to the backup server
and used to reconstruct the server if needed.
Robert Treat
conjecture: xzilla.net
consulting: omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
require compiling and implements that
feature.
Robert Treat
play: xzilla.net
work: omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
will be corrupt upon
server or OS crash (which is something most people should avoid).
> I think the only use of fsync off is for performance testing so see how
> expensive fynsc is.
>
Never speak in absolutes! ;-)
It's not unheard of to run with fsync = off when you have asynchro
ng. Personally I'd throw out
those vacuum cost settings entirely as they cause more trouble than
they're worth (IMNSHO), and you'll likely see this again in the
future.
Robert Treat
conjecture: xzilla.net
consulting: omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
idea in the past, though there
is a valid argument for saying that while you don't have a specific
limit you care about, there are values of length that are long enough
that they probably indicate garbage data or something gone wrong. In a
world where Postgres actually handled this problem
les to
the other destination.
Which method you want depends on the version / setup of postgres you
have, and whether you want the slave to be in the chain of the replica
site. (I probably wouldn't, which would make me lean towards something
like omnipitr)
Robert Treat
conjecture: xzilla.net
con
h. 50
(connections) x 128 (mb work mem) x 2 (sorts per query) = 12GB RAM,
which is 25% of total ram on the box. That doesn't necessarily mean
game over, but it seem like it wouldn't be that hard to get thrashing
being set up that way. YMMV.
Robert Treat
conjecture: xzilla.net
consulting: omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
w what type, how many, and in what
configuration? Also how is Postgres set up on top of the disks (all of
$PGDATA and OS on one volume? Split up?)
Also, how many active connections do you typically have? Can you
reduce your sort mem to something like 4MB, and set log_temp_files to
0?
Robert Treat
conjecture: xzilla.net
consulting: omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
old and crufty, but provides a good example:
http://labs.omniti.com/labs/pgtreats/browser/trunk/tools/zbackup.sh
[2] https://github.com/omniti-labs/omnipitr
Robert Treat
conjecture: xzilla.net
consulting: omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ther option for folks is to switch to another operating system thats a bit
more stable *cough*solaris*cough*bsd*cough*
:-)
--
Robert Treat
Conjecture: http://www.xzilla.net
Consulting: http://www.omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
so you can run your code unmodified.
>
*In theory* :-) There are still a number of shortcomings, so depending on how
large and/or complicated your systems are, it may or may not work for you,
but it's certainly worth a look if you're planning a migration.
--
Robert Treat
C
ny trigger
functions on the postgres side as well (or at least givec you a good starting
point to adapt it). HTH
--
Robert Treat
Conjecture: http://www.xzilla.net
Consulting: http://www.omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
While I would agree that these tools can't solve organizational problems, they
do exist:
http://pgdiff.sourceforge.net/
http://apgdiff.sourceforge.net/
http://www.dbsolo.com/
http://sqlmanager.net/en/products/postgresql/dbcomparer
there are others too...
--
Robert Treat
Conjecture:
rst_name FROM (select last_name, first_name from salesmen where
salesmen.id = accounts.sales_id) x
Which is great if you just want to get this done, but sucks if you wanted the
specific syntax from above.
--
Robert Treat
Conjecture: http://www.xzilla.net
Consulting: http://www.omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
id SERIAL PRIMARY KEY,
>table_changed regclass,
>changed_by VARCHAR,
>changed_when TIMESTAMP WITH TIME ZONE,
> );
>
> and then you have child audit tables for each audited table, each of
> which looks like this:
>
> CREATE TABLE audit_tablename (
>
that information is a bit out of date.
There's a better write up at
http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server
Once you go through that and restart, if it's still slow, can you paste
explain analyze from the two different servers?
--
Robert Treat
Conjecture:
ain lately, but if only 1% of your
rows are going to have data in this column, personally, I'd put it in a
separate table.
--
Robert Treat
Conjecture: http://www.xzilla.net
Consulting: http://www.omniti.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Wednesday 08 April 2009 15:30:28 Ian Mayo wrote:
> On Wed, Apr 8, 2009 at 8:13 PM, Robert Treat
>
> wrote:
> > Maybe I've been reading too much Pascal again lately, but if only 1% of
> > your rows are going to have data in this column, personally, I'd put it
>
On Wednesday 08 April 2009 18:25:25 Ron Mayer wrote:
> Robert Treat wrote:
> > You can be sure that discussion of this topic in this forum will soon be
> > visited by religious zealots, but the short answer is "nulls are bad,
> > mmkay". A slightly longer answer w
ot;pgsql-jp" is added to it. The list page is
> http://www.postgresql.jp/PostgreSQL/pgsql-jp.html.
Added, thanks much.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 5: Hav
afaik the Nerd Ranch guys can go either "fast or
slow" on the course depending on the aptitude of the students... if your
going to be sending multiple people it wouldn't hurt to talk with them.
HTH
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
t;
This has been fixed now, thanks for bringing it up.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscri
d of info
maybe, but they wont be out till summer at the earliest and more likely
the end of the year.
Of course this assumes you can do it at all ;-)
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)--
There's actually a list of recommended books up on techdocs:
http://techdocs.postgresql.org/#books
It could use a little updating, but is still pretty good.
Robert Treat
On Thu, 2005-03-24 at 09:57, Jeff Davis wrote:
> If you are looking for a database theory book, I highly recom
ing servicers have only MySql.
> Thats while I need an information about a hungarian (if you know) or
> non-hungarian free webhosting service with postgreSQL.
>
> Thank you in advance!
>
>
I don't know of any... does anyone else?
Robert Treat
--
in the order of PHP,
PostgreSQL,plPHP which is the same for all of the other pl's.
You don't need postgresql installed before php any more than you need it
installed for perl (although you do need postgresql installed to compile some
of the perl & php db interfaces, but th
On Mon, 2005-04-04 at 16:17, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > On Monday 04 April 2005 12:01, Tom Lane wrote:
> >> Peter has pointed out that the problem of circular dependencies is a
> >> showstopper for integrating plPHP.
>
>
On Mon, 2005-04-04 at 17:00, Doug McNaught wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
>
> > If by "stripped down" you mean without postgresql database support then
> > I'll grant you that, but it is no different than other any other pl
> > wh
On Mon, 2005-04-04 at 17:03, Alvaro Herrera wrote:
> On Mon, Apr 04, 2005 at 04:48:50PM -0400, Robert Treat wrote:
>
> > If by "stripped down" you mean without postgresql database support then
> > I'll grant you that, but it is no different than other any o
e ability to use my$ql... I'd guess that this is because
most php programmers are more familiar with my$ql and my$ql still holds
the edge on the number of third party apps that often get used on free
hosting services like these.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middl
es *NOT* require a dump restore, but due to a bump
> > in the major version number for the client library (libpq), it *WILL*
> > require all client applications to be recompiled at the same time.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware}
ouch upon and then see about
reengineering those particular parts of the schema. The bit by bit approach
should get them to the same end game with stalling development for the next
few months. Make sure to make use of views and stored procedures to help
keep backwards compatibility where
omething like that rather than creating a
surrogate key... so just because they have done that doesn't mean that they
are wrong even if your way is better.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 8: explain analyze is your friend
NULL and
thats why the boolean type is still in the extended set of sql spec and
not core.
Inceidentally MySQL's boolean is really scary... it's not just than 0 =
false and 1 = true, its 0 = false and (n >= 1) is true. IMHO that
sounds like a recipe for creating subtle bugs.
Robert
the
> > > database, then to the tables, then to the sequences.
> >
> > In this case, why not let 'username' create the database and all its
> > objects so that it will have all privileges on them afterwards without
> > any specific GRANT required?
>
> T
pefully it will
get done. Also the workaround is to create a regular trigger and then do
a check in the function
IF NEW.mycol <> OLD.mycol THEN... it's not quite as spiff but should do
what you want.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
-
27;d like to think it's not optimistic --- but yeah, Thanksgiving-ish is
> a reasonable bet.
Perhaps we should add a couple of lines to the TODO stating that feature
freeze is planned for july 1 and give estimated times for phases to follow?
This could help people to determine how fea
uld be to use slony, which would minimise the down time, but might
not fall into the "without much work" constraint.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 8: explain analyze is your friend
ll late fall at the earliest afaik, so those are probably your best
choices.
Robert Treat
On Friday 03 June 2005 17:23, Bob wrote:
> I think it hits the press in June or July 2005???
>
> On 6/3/05, Brad Nicholson <[EMAIL PROTECTED]> wrote:
> > Gevik babakhani wrote:
> >
you could leave in the
quotes from the previous emails where we say pretty much the exact same thing
only with more detail and actually useful information, it would really be
something.
:-)
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---
actually reference plpgsql,
so if you're interested in that kind of traffic, you might want to subscribe
there.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Anyone else getting duplicate messages? I seem to be getting them
sporadically on different messages on pgsql-general. Seems to have started
sometime Monday morning (estern us time)
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end
ening on
one of my subscribed emails, not the other, which is a little weird...
according to the headers though, this problem is happening further
upstream.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)
On Wednesday 27 July 2005 12:30, Alvaro Herrera wrote:
> On Wed, Jul 27, 2005 at 11:46:05AM -0400, Robert Treat wrote:
> > Seems unlikely unless folks like Tom Lane, Stephan Szabo, and Richard
> > Huxton have unsubscribed and resubscribed lately... Funny thing is it
> > isn
cation needs.
> Combine slony with pgpool and a few scripts and you've got quite a nice
> cluster setup.
>
Can someone point me to the multi-master replication docs for my$ql 4.1? I
agree with Scott, sounds like they are looking for an excuse.
--
Robert Treat
Build A Brighter L
ter
> even if I use oid instead of ctid.
> Inner query works promptly of course.
>
> Any clue?
>
I think using an indexed field would probably be faster for you, especially if
you have a PK on the table. Barring that, make sure you have
vacuumed/analyzed and send us explain analyze
eneral I'd agree with you, but I've seen a couple of (some
would say hackey) use cases where you use the ctid to iterate over the
columns returned in a row in a plpgsql function... :-)
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
-
http://www.bizgres.org/pages.php?pg=downloads
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
seperates the data loading piece from the piece where you promote
the data to live data, plus then the time you have to hold the
transaction open is only for the drop and rename, which will be quite
fast.
the only potential issues would be making sure you dont have FK/View
type issues, but it d
in PostgreSQL..."
>
I think I concur with you on that one Richard... fixed in CVS, will go live on
next site build. Thanks.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
NULL,
tb_ex TEXT,
tb_name VARCHAR(255),
INDEX (tb_page)
);
I couldn't figure out why they weren't specifying type = innodb for the table,
but then figured they must have declared it some place else or something...
but now I see that even that w
, PostgreSQL makes use of some
elements of NTFS which is not supported by win98. To be honest, I believe
you could hack things to get around this, but it's probably not worth the
effort / possible stability issues.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} Postg
nce pg
can't optimize complex queries into the inital query to set up the view.
Not sure if my$ql is any smarter about this, but that's the first thing to
look for if you were to investigate how well it worked.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} Post
e wants to step up to it), why not setup the bug tracker, work with
> > the -www guys on having the 'bug submission' stuff feed into it, and get
> > a
>
> ...
>
> Btw. how do you work with the WWW guys? I _never_ ever got any answer.
>
What did you ask?
plications (think erp and
crm) that my$ql has been targeting to be able to support with 5.0 that would
compete directly with oracle (by way of giving those application vendors
leverage to use my$ql instead of oracle). Part of a future licensing
agreement might be that my
site content / correction are
best sent to pgsql-www or webmaster. If you post elsewhere, we'll probably
see it, but it might take awhile.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)--
me to make sure there are no
schema issues or application issues on the new db. Don't forget to time the
process so you can plan your outage accordingly.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
my guess is that they started reading up as soon
as .org was awarded to a pg based company. I think before that they
probably figured that my$ql, being more popular, was roughly equal if not
better than postgresql, and often confused the two. If there smart enough to
be buying innobase
enterprisedb :-)
> 2) Some sort of FUD campaign on the part of Oracle directed
> specifically at us and not tied to any specific project (fairly likely).
>
look for pointers to lack of benchmarks, patent issues, and great bridge...
those seem to be the most common rehash of fud.
--
R
stalling / compiling. I didn't use the ports
> system though..
>
I can't find the upstream post, but I wonder if some of the articles on
freebsd diary might help? They're a bit old, but I think the general
info still applies: http://www.freebsddiary.org/topics.php#postgre
p and getting it in officially; One concern I had was finding a way to
include information that won't bog down end users with too much data.
(I've noticed large numbers of points tend to do that)
Robert Treat
On Tue, 2005-10-25 at 12:11, Claire McLister wrote:
> Thanks.
>
> I look
st a slew of encodings...I'd start
there.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail
the switch was made. That's how the snowball effect starts, and you can
bet oracle is trying to nip these things in the bud.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: explain analyze is your friend
; version).
>
By my math 7.4.2 > 7.3.x so slony should work in the above scenario.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will
he first edition which was very good; it's material is
probably a bit more intermediate level.
Otherwise there is a list of PostgreSQL related books available at
http://www.postgresql.org/docs/books/ which contains links to older books and
books online. HTH.
--
Robert Treat
Build A
owever very strict
> with what license they allow.
>
> Wikipedia commons only allow images licensed as Public Domain or GPL.
That's goofy... the wikipedia "commons" wont accept creative commons licenses?
That's what we've licesed all of the new logos under...
http://www.p
On Fri, 2005-11-11 at 12:01, Andreas Kretschmer wrote:
> Robert Treat <[EMAIL PROTECTED]> schrieb:
> > > Anyway I am open to some good recommendations.
> >
> > I think I would recommend "Beginning Databases with PostgreSQL, 2nd
> > Edition"
> &g
gt; > than some community product called PostgreSQL? (And yes, I suspect
> > there _are_ such people.)
>
> Maybe he is going to call it "Orakle"? :)
>
I was thinking he could call it "my-sql"...
Robert Treat
--
Build A Brighter Lamp :: Linux
the posting of the autonomous transactions and then calling those
inside your functions.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
101 - 200 of 339 matches
Mail list logo