nd I
mighta traded them for a lump of pig iron, they were so flakey.
Having "Sun" on the outside in no way protects you from faulty
hardware.
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
http://www.commandprompt.com/
--
Sent via pgsql-general mailing list (pgsql-gener
for the same database using shared
storage?" the answer is, "No."
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
http://www.commandprompt.com/
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
OK copy a "slice" of the snapshot in *other*
> tables.
This is more than one statement. So you will be able to see changes
in between those statements. If you don't care about that, then your
approach will work.
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
ht
throws
an error). That means _before_ you call the first function (since
calling the function is then the first statement in the transaction,
before serializable).
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
http://www.commandprompt.com/
--
Sent via pgsql-general mailing lis
On Fri, May 16, 2008 at 09:06:11AM +0200, Ivan Sergio Borgonovo wrote:
> Is
> BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE
> what I'm looking for?
Yes.
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
http://www.commandprompt.com/
--
Sent via pgsql-general maili
On Fri, May 02, 2008 at 09:57:58PM +0200, Tino Wildenhain wrote:
> apt-get install postgresql-8.1 gives you 8.1 in etch (stable)
> in addition to 7.4.
Huh. Debian gets more inscrutable every time I fail to look.
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x10
with 7.4. I thought that at _least_ 8.0 was out
prior to freeze. What happened?)
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
http://www.commandprompt.com/
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
art up a new
postmaster at this point, you will corrupt your data almost certainly.
Why are you allowing memory overcommit at all? And what is causing
you to swap? I think those are the things you need to fix.
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
http://www.commandpr
ome with or have available for them spare parts,
schematic documents, and long warranties. The latter come with, if
you're lucky, a warranty of a year and warnings that there are no
servicable parts inside. Yet people expect to use their toasters and
kitchen gadgets for years, and are annoyed if
re
you do this. (The docs in fact tell you how to do it, but you have to
read two parts of the docs to figure it out. I am trying to
discourage you from doing what you're planning, so I'm unwilling to
tell you how to do it.)
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
any oddly specialised
tool, they require careful use.
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
http://www.commandprompt.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 Fri, Apr 25, 2008 at 12:29:48PM -0400, Jimmy Choi wrote:
> Thanks. I'm not really in a position to upgrade at the moment.
You know that an upgrade of 8.1 to the latest is not a dump and restore, and
that running an older stability-and-security release of the software is
probably more dangerous
On Fri, Apr 25, 2008 at 02:14:17PM +0200, Aleksander Kmetec - INTERA wrote:
> Is there a way to get the time of the last insert, update or delete
> statement for a specific table?
Only if you put a trigger on each table to collect that information.
A
--
Sent via pgsql-general mailing list (pg
On Thu, Apr 24, 2008 at 11:04:10AM -0500, D. Dante Lorenso wrote:
>
> Or, here's another way to look at it ... make it easier to modify ENUM
> datatypes because we all know that you will eventually need that feature
> whether you males, females, and unknowns think so or not.
Well, heck, why don
On Wed, Apr 23, 2008 at 07:46:07PM -0400, brian wrote:
>
> Absolutely true. Which is odd, because this example is trotted out
> whenever there's a thread about ENUMs.
I don't think it's odd at all. In my view, the people who think enums are a
good datatype for databases are exactly the sorts wh
On Fri, Apr 18, 2008 at 11:15:09AM -0700, Joshua D. Drake wrote:
> sync transaction have to run? You know vacuum isn't working while
> that transaction is open right? Are you going to have to setup up a
> dozen different replicated sets in order to get it done?
A dozen sets isn't really a big de
Oh, one other thing
On Thu, Apr 17, 2008 at 12:44:51PM +0800, Craig Ringer wrote:
> > One way I can think of doing it is to write a seen_log that notes what the
> > client has already seen with a timestamp of (say) 1 minute. Then you can
> > say "go forward from this time excluding ids (ids her
On Thu, Apr 17, 2008 at 12:44:51PM +0800, Craig Ringer wrote:
> It won't work with multiple concurrent writers. There is no guarantee
> that an INSERT with a timestamp older than the one you just saw isn't
> waiting to commit.
This is pretty unlikely -- I won't say impossible, because I'm sure the
On Thu, Apr 17, 2008 at 12:35:33AM +0800, Craig Ringer wrote:
> That's subject to the same issues, because a transaction's
> current_timestamp() is determined at transaction start.
But clock_timestamp() (and its ancestors in Postgres) don't have that
restriction. I dunno that it's enough for yo
On Fri, Apr 11, 2008 at 03:09:43PM +0200, Stefan Sturm wrote:
> DBVisualizer stoped working and no I have two processes on my server:
> postgres 30873 0.0 0.7 46552 7124 ?Ss 12:33 0:01
> postgres: postgres dbName 10.0.1.198(53658) ALTER TABLE waiting
> postgres 31007 0.0 0.6 46
On Tue, Apr 08, 2008 at 02:39:32PM +0300, Sim Zacks wrote:
> Is there any way to do a dirty select to find out what a process is up
> to?
No.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-gen
On Wed, Apr 02, 2008 at 02:42:08PM -0400, Morris Goldstein wrote:
> (Why not give postgres its own volumes? Long and not very interesting story.)
But relevant to this case. I think you need to give it its own volumes.
A
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To
On Wed, Apr 02, 2008 at 05:49:37PM +0100, Ian Sillitoe wrote:
> Unless I've missed something, the docs on
> http://www.postgresql.org/docs/8.1/static/functions-comparison.html seem to
> suggest that the concept is an example of bad programming and the workaround
> (of switching on the 'transform_nu
On Thu, Mar 27, 2008 at 10:41:52PM -, Greg Sabino Mullane wrote:
>
> For the record, I think any renaming is a terrible idea, and a solution
> in search of a problem. Any change, no matter how long it takes, will
> break untold number of scripts, make us look bad, and frustrate
> people, simil
On Wed, Mar 26, 2008 at 01:03:34AM -0400, Greg Smith wrote:
> against. People who are using the current warm-standby code are already
> grappling with issues like how to coordinate master/slave failover
> (including my second favorite acronym, STONITH for "shoot the other node
> in the head").
On Tue, Mar 25, 2008 at 02:51:05PM -0400, Edward Blake wrote:
> CREATE RULE timestamp_update AS ON UPDATE TO visit
Do this with a trigger instead of a rule. I think there's an example in the
docs of something very similar, but I haven't checked just now.
A
--
Sent via pgsql-general mailing li
On Thu, Feb 28, 2008 at 08:38:26AM -0500, Merlin Moncure wrote:
>
> > I'm using Zonealarm firewall but Postgres is authorized on 127.0.0.1:5432.
Sorry, I missed this in the OP. But I've had people tell me that Zonealarm
causes them problems even if it's completely turned off. One person told m
On Fri, Feb 22, 2008 at 11:50:51AM -0300, Carlos H. Reimer wrote:
> Hi,
>
> I´ve noticed in my Fedora Core 6 box running PG 8.2.3 that column
> current_query of pg_stat_activity view is not showing the complete query.
Yeah, it can't show very long queries. I forget what the length restriction
is
On Fri, Feb 22, 2008 at 03:29:31PM +0100, [EMAIL PROTECTED] wrote:
> Hi All.
> Anyone knows if rebuilding the postgresql sources with the flag
> --without-tcl --without-perl in ./configure filecan prevent the correct use
> of the triggers wrote in plpgsql language?
PL/pgSQL has nothing to do with
On Thu, Feb 21, 2008 at 04:35:28PM -0500, Geoffrey wrote:
> How might we find out which release it was fixed in? Back patching
> 7.4.19 with the fix might be easier then trying to move up to the fixed
> version.
According to HISTORY, there was a significant fix in this area in 8.1:
* Add "
On Thu, Feb 21, 2008 at 01:03:13PM -0500, Tom Lane wrote:
> to disable just some triggers. I think the bug you are remembering is
> that there's always been a pg_trigger.tgenabled field, but it wasn't
> always honored everywhere,
You're quite right. My apologies. (Especially since I've now repe
On Thu, Feb 21, 2008 at 12:49:48PM -0500, Terry Lee Tucker wrote:
>
> Thanks for the input. I've been using the reltriggers in pg_class for a long
> time and it does work; however, I did notice in the documentation on
> pg_trigger that tgenabled is not checked properly and using that will give
On Thu, Feb 21, 2008 at 11:44:25AM -0500, Terry Lee Tucker wrote:
> table where, when the given trigger does fire, it checks for an entry in the
> table at the top of the trigger and takes the appropiate action. The problem
> is that the solution for disabling all triggers is used in several uti
On Sat, Feb 16, 2008 at 10:38:56AM -0500, Arturo Pérez wrote:
> HI all,
>
> The news/NNTP feed to these mailing lists does not seem to be working.
No, the news server's been broken for a while.
A
---(end of broadcast)---
TIP 3: Have you checked ou
On Fri, Feb 15, 2008 at 09:09:32PM +0800, Phoenix Kiula wrote:
> Actually my host has just told me that I have a number of "hung
> semaphores" in my server. And he is relating them to postgresql. I am
> not surprised, because this is the only utility that has issues. All
> the rest is working (apac
On Sat, Feb 16, 2008 at 12:38:04PM +0800, Phoenix Kiula wrote:
> My hosting provider tells me that the Postgresql server is taking up a
> lot of memory but I've been running the same db with the same config
> for over 2 years. Yes we have been growing but what happened in the
> last 3 days to warr
On Tue, Feb 12, 2008 at 08:39:05PM -0700, Ken Johanson wrote:
> between 3rd party products (customer API and database x^n). I'm trying
> to convey here that changing the behavior to a (numb AS varchar) one,
> practically speaking, is more benign/useful (vs now), even if that is
> only a non-spe
On Tue, Feb 12, 2008 at 09:44:30AM +0100, Ivan Sergio Borgonovo wrote:
>
> That's why I wrote "without making it too formal" and "bland
> commitment to the release schedule...".
The problem with doing it that way is that, when the release fails to meet
the original target deadline, any coverage o
On Mon, Feb 11, 2008 at 10:38:55AM -0800, Bob Pawley wrote:
> All of my tables are without oids.
>
> I have an application in which I drop, then recreate a table (to reset
> serial numbers) and with an update on the new information I get an error
> about a specific oid missing.
>
> Any thoughts
On Mon, Feb 04, 2008 at 06:52:42AM -0800, Selena Deckelmann wrote:
> Having a separate TLD actually increases the visibility of the effort
> from a search engine perspective.
Having just come from the domain name industry, I can report that that's
only sort of true. Did you "taste" this domain fo
On Fri, Feb 01, 2008 at 11:17:19AM -0800, Reece Hart wrote:
>
> Does anyone know of an authoritative, complete, and current license
> comparison? After a lot of trolling, I've been able to satisfy one or
> two of those criteria, but not all.
The FSF has maintained a list of many licenses for year
On Tue, Jan 29, 2008 at 03:16:41PM -0500, A.M. wrote:
> ...and Pg.pm includes a serious security hole in the form of non-
> existent query escaping which will never be fixed. Are we really
> discussing the semantics of "rust"?
It has never done that escaping. No rust has occurred. This is a
On Tue, Jan 29, 2008 at 01:56:35PM -0500, A.M. wrote:
> The postgresql from eight years ago is also quite rusty.
No, it's not, which is my point. If you don't need any of the features you
mention, and are aware of the limitations, there's nothing wrong with
using it. The v2 protocol works, for i
On Tue, Jan 29, 2008 at 08:14:28AM -0800, David Fetter wrote:
>
> I wouldn't trust that library or anything that depends on it if I were
> you. It's been unmaintained for a *very* long time.
Because code rusts when it's sitting around on a hard drive?
Pg.pm doesn't get much attention, I agree,
On Tue, Jan 29, 2008 at 04:24:05AM -0800, Glyn Astill wrote:
> Hi chaps,
>
> I'm trying yo run a perl script that uses DBI (Slonys
> psql_replication_check.pl to be precise) and I'm getting the error:
>
> Can't locate Pg.pm in @INC
Pg.pm isn't DBI. It's the Pg Perl interface.
A
--
On Fri, Jan 18, 2008 at 04:09:45PM +, [EMAIL PROTECTED] wrote:
>
> That's just it - I don't think any user-land libraries would actually be
> required. One of supposed big advantages of MySQL is it's straightforward
> replication support. It's quite painful to see PostgreSQL suffer purely
>
On Fri, Jan 18, 2008 at 03:14:41PM +0800, Ow Mun Heng wrote:
> Just wondering if my 'Perceived' feeling that since implementing slony
> for master/slave replication of select tables, my master database
> performance is getting slower.
It imposes a performance penalty, yes.
A
---
On Thu, Jan 10, 2008 at 11:08:16AM -0500, Andrew Sullivan wrote:
> I mean this sincerely and not snidely: get another job. 7.3.20 was the last
Err, 7.3.21, I meant, of course. Sorry.
A
---(end of broadcast)---
TIP 4: Have you searched our l
On Wed, Jan 09, 2008 at 06:19:40PM -0500, Brown, Richard wrote:
>
> - We are using PostgreSQL 7.3.4, and am locked into this version. I would
> upgrade if I could, but the decision is not mine.
I mean this sincerely and not snidely: get another job. 7.3.20 was the last
release in the 7.3 series.
On Wed, Jan 09, 2008 at 12:38:43PM -0700, Guido Neitzer wrote:
> >>Easy multi-master clustering with just two machines.
> As I said: FrontBase is offering that.
It looks like a two-phase commit answer, if I'm reading correctly. You can
do this today on many systems (including Postgres), but the
On Wed, Jan 09, 2008 at 12:24:37PM -0500, Josh Harrison wrote:
> For example if I have a query like
> select column2 from ABC where column1 > 20
> and table ABC is indexed on (column1,column2) then Oracle will not goto the
> heap to fetch the tuples. It will return them from the index itself since
On Tue, Jan 08, 2008 at 10:59:56PM -0700, Guido Neitzer wrote:
>
> Easy multi-master clustering with just two machines.
To my knowledge, _nobody_ actually offers that.
There are three companies I know of that have done effective marketing of
systems.
Company O has a very advanced system with pl
On Wed, Jan 09, 2008 at 11:03:59AM -0600, Scott Marlowe wrote:
>
> And if, for some god forsaken reason, you need to operate on that
> number, there's always "lock table"...
Yes. You could also store the data in ISAM :-P
> I feel dirty. :)
You should. Go wash your brain out with soap. LOCK T
On Wed, Jan 09, 2008 at 11:51:16AM -0500, Josh Harrison wrote:
> accessed frequently. So clustering the table according to one index will
> yield poor performance to queries involving other indexes.
Maybe not poor, but certainly not optimised.
> Index-only scan is a good solution for this I gue
On Wed, Jan 09, 2008 at 05:21:24PM +0100, Ivan Sergio Borgonovo wrote:
>
> I got the impression that even counting with clauses on on indexed
> columns means you'll have to check if columns are still there. That
> seems to imply that the extra cost make pg under perform compared to
> other DB even
On Wed, Jan 09, 2008 at 05:28:15PM +0100, Ivan Sergio Borgonovo wrote:
> Does it make any sense *knowing* how the implementation works to load
> records in a table in a specific order to improve performances?
Well, this is more or less what CLUSTER does. There are some cases where
happening to kn
On Tue, Jan 08, 2008 at 11:37:38PM -0700, Guido Neitzer wrote:
> Like, I have a situation where I need multi-master just for
> availability. Two small servers are good enough for that. But
> unfortunately with PostgreSQL the whole setup is a major pain in the ...
Really? I don't think a RAID
On Mon, Jan 07, 2008 at 12:58:44PM +0100, Michelle Konzack wrote:
> > except he has large objects, which slony can't replicate.
>
> currently or will this be changed in the future?
Not likely to change in the future, no. Slony uses triggers to manage the
changed rows. We can't fire triggers on
On Tue, Jan 08, 2008 at 01:49:53AM +1100, Naz Gassiep wrote:
> Because doing normal queries on a table where there are large text
> blocks is unlikely to be a good idea. E.g.,:
>
> SELECT * FROM table WHERE textcol = 'a 4kb block of text';
I suggest you look at the tsearch stuff instead.
> I wo
On Fri, Jan 04, 2008 at 06:11:40PM -0300, Alvaro Herrera wrote:
> swooping elephants must be an interesting sight. If pigs can fly ...
Is this what you had in mind?
http://www.amoeba.com/dynamic-images/blog/dumbo.gif
A
---(end of broadcast)---
TI
On Thu, Jan 03, 2008 at 11:15:23AM +0800, Ow Mun Heng wrote:
> I'm just wetting my hands with slony and during the setup of the slave,
> I did and dump and restore of the master DB to the Slave DB.
Nope, you don't need to do that. You need a copy of the _schema_ on the
target machine. But slony
On Fri, Dec 28, 2007 at 12:06:42PM -0500, Josh Harrison wrote:
> I also thought abt having 2 setups for backup and replication so that even
> when slony fails I will always have the standby server (WAL shipping) to
> help me out.
Ok, but do realise that what this form of redundancy provides you wi
Along with the other good remarks people have made, I want to point
something out.
On Tue, Jan 01, 2008 at 06:49:40PM -0800, Chuck wrote:
>
> I created a test database and confirmed that it's created with
> 'SQL_ASCII' encoding.
> [EMAIL PROTECTED] ~]# sudo -u postgres createdb myTest
> could no
On Tue, Jan 01, 2008 at 06:05:32PM +0100, Tomasz Ostrowski wrote:
> > LC_CTYPE="POSIX"
> > LC_COLLATE="POSIX"
>
> This is bad. Make sure you have
> LANG="en_US.UTF-8"
> set in a file "/etc/sysconfig/i18n" and reboot.
If you do it that way, be _very sure_ you understand the interactions of
l
On Mon, Dec 31, 2007 at 02:39:02PM -0800, Chuck wrote:
> yum -y install postgre postgre-server postgre-devel
I assume that's all spelled "postgres". But otherwise, ok.
> Upgrade to PostgreSQL 8.2.5?
> Before I start creating databases, it seems like I should up consider
> upgrading to PostgreSQ
On Fri, Dec 28, 2007 at 11:21:53AM +0100, Florian Weimer wrote:
> This only helps against crasher bugs. For code injection, it's
> devastating if the attacker can compromise one node, and by
> diversifying, he or she can choose which code base to attack.
Well, it also helps in your robustness p
On Thu, Dec 27, 2007 at 01:08:50PM -0500, Andrew Sullivan wrote:
> Note: I've removed -general, since this is really just a Slony discussion.
err, except I didn't. Apologies for the noise, all.
A
---(end of broadcast)---
TIP 9: In v
Note: I've removed -general, since this is really just a Slony discussion.
On Thu, Dec 27, 2007 at 12:49:55PM -0500, Josh Harrison wrote:
> We wanted to have 1 master and 1 slave that can be queried and 1 warm
> standby server that can be brought up in case of crash. So I thought it
> might be be
On Thu, Dec 27, 2007 at 10:49:10AM -0500, Josh Harrison wrote:
> Hi,
> We are trying to use slony and WAL shipping for warm standby for replication
It's unusual to use both. Any reason you want to?
Anyway. . .
> What are the other large 24x7 productions systems that use slony and the
> other WA
On Wed, Dec 19, 2007 at 10:38:52AM -0500, Tom Lane wrote:
> reading the password from /dev/tty, so if you want to script this, you'd
> be stuck with making a special-purpose program that didn't.
But given that passwords are sort of awful in this way anyway, why not use
something designed not to ha
On Wed, Dec 12, 2007 at 12:28:37PM -0800, pilzner wrote:
> thats what I'm familiar with" discussion, just to get a feel of why its done
> that way, if I'm doing anything wrong, or if there is an accepted way to
> lock it down.
It'd be easy to lock down with a trigger that RAISEs ERROR in case OLD
On Tue, Dec 11, 2007 at 07:44:31PM +, Gregory Stark wrote:
> Seriously, do you have any trouble following the discussion even though I
> only clipped two sentences of your message? If you did would you have any
> trouble finding the original message to reread it?
No, but (1) I have been doing
On Tue, Dec 11, 2007 at 09:00:05AM -0800, Joshua D. Drake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tue, 11 Dec 2007 11:49:54 -0500
> Andrew Sullivan <[EMAIL PROTECTED]> wrote:
>
> > On a mailing list, perhaps one can argue that the con
On Tue, Dec 11, 2007 at 08:43:44AM -0800, Joshua D. Drake wrote:
>
> O.k. this might be a bit snooty but frankly it is almost 2008. If you
> are still a top poster, you obviously don't care about the people's
> content that you are replying to, to have enough wits to not top post.
There are those
On Wed, Dec 05, 2007 at 12:53:45AM -0500, Greg Smith wrote:
> The issue Andrew is bringing up here is that really new PostgreSQL
> versions probably aren't necessairly backward compatible talking to or
> reading dumps from your 7.0 system, so your odds are better trying to
> upgrade to 7.3 inste
On Tue, Dec 04, 2007 at 02:21:43PM -0500, Gauthier, Dave wrote:
> Is there something like a freeware windows client app that does DBA
> stuff for a remote server? Sort of like TOAD for Oracle?
TOAD either does or used to work for Postgres.
A
---(end of broadcast)---
On Mon, Dec 03, 2007 at 03:20:45PM -0600, Ed Burgstaler wrote:
> Would anyone be able to direct me as to whether or not there is a pgadmin
> for windows utility available that will work for a PostgreSQL v7.0.3
> database?
Not to my knowledge. But I wouldn't spend any time on it -- you need to ge
On Mon, Dec 03, 2007 at 04:16:04PM +0100, Pascal Cohen wrote:
> needs fast connections like fiber channels ? What is the impact on I/O
> and general DB perfs ? - Sorry if my question is stupid - not an expert
> on such things.
> And I suppose it is not very cheap ;)
Well, if you think you're goi
On Mon, Dec 03, 2007 at 09:57:30AM +0100, Pascal Cohen wrote:
> >
> What kind of hardware solutions do you know ? - I will look on my own
> what I can find.
Have a look at the discussion in the 8.3 manual, about shared disk and block
level replication:
http://www.postgresql.org/docs/8.3/static
On Mon, Dec 03, 2007 at 09:16:40AM +0100, Pascal Cohen wrote:
>
> * For High-availability, I mainly studied PgPool and Log-shipping (and
> in fact forgot Slony).
> Until now I feel more comfortable with Log-shipping because it seems
> safer (I am not sure I can't get some problems with sequences
On Fri, Nov 30, 2007 at 10:30:47PM +0100, Pascal Cohen wrote:
> I am facing a probably very common problem. I made a search in the
> recent archives and could find many posts related to my issue. But I did
> not get exactly "the answer" to my question.
No, and I doubt you will.
> But I don't kn
the same research lab, is all.
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROT
fight, I think
you need to have a long talk with your corporate counsel :)
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Thu, Nov 29, 2007 at 12:48:35PM -0500, Tom Lane wrote:
> Andrew Sullivan <[EMAIL PROTECTED]> writes:
> > The general tone in this thread sounds like, "I don't have time to
> > administer this; help me." Providing such help is a bad idea.
>
> Actua
there is nice,
because it provides things that the poastmaster alone may know; but
additions would be gilding the lily, except with pyrites).
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---(end of broadcast)---
T
no. That sounds like a way to suppress useful error messages when
something Really Bad is happening. As it happens, that's when the flood of
messages is most important.
The general tone in this thread sounds like, "I don't have time to
administer this; help me." Providing suc
On Mon, Nov 26, 2007 at 11:57:37PM -0800, Alagu Madhu wrote:
> Which is the best Stored Procedures or Dynamic SQL generated by ORM ?
This is roughly similar to the question, "Is it better to travel by car,
boat, or plane?" It rather depends on what you're trying to accomplis
's wrong with
Slony? My employer developed and released it because our business depended
on this functionality. That you can get to postgresql.org today proves that
it's working.
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---
any
day within the next 5 years. (Beyond that, I'm unwilling to speculate.)
Tricky problems require expensive tricks. See the manual for tricks you can
perform today. Hint: PostgreSQL depends on the OS, so using OS tricks is an
option.
A
--
Andrew Sullivan
Old sigs will retur
n order to get that value, you
have to have all -- ALL -- transactions on all nodes in SERIALIZABLE mode.
Is that ok?
Then talk to Markus. He's a smart guy. He needs someone to help him make
his work public.
A
--
Andrew Sullivan
Old sigs will return after re-constit
d to restart?
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Thu, Nov 22, 2007 at 02:43:02PM +0100, [EMAIL PROTECTED] wrote:
> Yes, there is a different connection for each thread :-(
So do you have some autocommit setting incorrect?
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---(end
then it works on your system :) I just
wanted to warn you that this isn't an original feature of cron, so you have
to check your system always to be sure you have it.
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---(end of broadcast)
cron, which does accept that, but some don't. It's a nice feature,
and good for this purpose.
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---(end of broadcast)---
TIP 1: if posting/reading thr
t;BEGIN;");
Uh, are your two threads using one connection? That's never safe.
> The same commands (inside the same code) runs fine in Windows and in MacOS
> X.
If you're using one connection and two threads, this is some accident of the
client, and nothing more.
A
-
On Wed, Nov 21, 2007 at 12:20:51PM -0800, Garber, Mikhail wrote:
> In the high-availabilty situation with a warm standby, is it possible (or
> planned) to be able to make standby readable?
Yes, but it won't happen for 8.3. It's a feature you can have today with
Slony, by the way
#x27;t think that a build system, along with
change control, for your schema is a good thing?
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
On Fri, Nov 16, 2007 at 02:02:37PM -0700, Ed L. wrote:
> subtree of view dependencies just to change one minor aspect of
> an independent view.
Well, it's not independent, if other things depend on it, is it?
:)
A
--
Andrew Sullivan
Old sigs will return after re-constitution of
erformance first, I think.
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
ssibility you have Slony installed? Is this a replica? If
so, it's a well-known problem. You can't use pg_dump under those
circumstances.
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
---(end of broadcast)--
301 - 400 of 733 matches
Mail list logo
