Greg Smith wrote:
[...]
-Find something harmless I can execute in a loop that will generate WAL
activity, run that until the segment gets archived. Haven't really
thought of something good to use for that purpose yet.
Some time ago I started a thread about taking on-the-fly backups at file
l
Greg Smith wrote:
On Thu, 31 May 2007, Marco Colombo wrote:
archive_command = 'test ! -f /var/lib/pgsql/backup_lock Under normal condition (no backup running) this will trick PG into
thinking that segments get archived. If I'm not mistaken, PG should
behave exactly as if no archi
Greg Smith wrote:
The way you're grabbing
files directly from the xlog directory only works because your commit
workload is so trivial that you can get away with it, and because you
haven't then tried to apply future archive logs.
Well, it's only because I don't need future logs, just like I
Simon Riggs wrote:
> Marco Colombo wrote:
my method
...is dangerous
Ok, but why? Once again, I'm asking: what _exactly_ can go wrong?
> so we don't get loads of new DBAs picking up this idea
but missing the exact point of danger.
I'm one of them. I'm _am_ missing
Greg Smith wrote:
On Tue, 5 Jun 2007, Marco Colombo wrote:
AFAIK, files in pg_xlog are first renamed (and only if and after the
archive_command returned true) and later overwritten to. Never deleted.
No, they get deleted sometimes, too. Not often, but it can happen under
heavy load if more
Simon Riggs wrote:
On Tue, 2007-06-05 at 18:39 +0200, Marco Colombo wrote:
I'm asking: what _exactly_ can go wrong?
If a checkpoint occurs while taking the backup then the contents of the
files will be overwritten
^
Data files or WAL segments? My archive command prevents WAL seg
Gabriele wrote:
I'm going to develop a medium sized business desktop client server
application which will be deployed mostly on small sized networks and
later eventually, hopefully, on medium sized networks.
It will probably be developed using C#.
I do need a solid DBMS wich can work with .Net f
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] writes:
My database has shutdown several times in the last couple days. I have
no
idea why. I am running centos and I have not rebooted the server or
made
any configuration changes.
Oh, I forgot. You do have plenty of swap space compared to RAM, yes
ter.
If you do, it's a hard call. If you think about it, the funny thing is
that the more experienced the sysadm you're talking to is, the less
experience he has about handling OOM situations. By definition. :)
.TM.
--
/ / /
/ /
Csaba Nagy wrote:
> First of all, thanks for all the suggestions.
>
>> put a SERIAL primary key on the table
> Or:
>> Maybe add OIDs to the table, and delete based on the OID number?
>
> No, this is not acceptable, it adds overhead to the insertions. Normally
> the overhead will be small enough,
Cultural Sublimation wrote:
>> Unfortunately for you, they are not different types. If the OCaml
>> binding thinks they are, it's the binding's problem; especially since
>> the binding seems to be using a completely lame method of trying to tell
>> the difference.
>
> Hi,
>
> In OCaml and in oth
; getting an error.
If you remove the privs, clients will get an error, unless I'm missing
something.
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / /
Andrus wrote:
>> Under what interpretation would the results differ?
>
> Results must differ for easy creation of LinQ-PostgreSQL driver.
> If results are always the same , PostgreSQL should not allow to use both
> order of clauses.
>
> Nicholas explains:
>
>Assuming the ordering is the same
On 11/04/2010 04:00 PM, Michael Gould wrote:
I know that this is probably a "religion" issue but we are looking to
move Postgres to a Linux server. We currently have a Windows 2008 R2
active directory and all of the other servers are virtualized via VMWare
ESXi. One of the reasons is that we want
On 11/09/2010 02:31 AM, Carlos Henrique Reimer wrote:
Hi,
I'm currently in the process of moving the data from the Windows server
to the new Linux box but facing some problems with the encoding.
Additional configuration information: Windows is running PG 8.3 and the
new Linux box is PG 8.4.
Wi
On 03/31/2011 09:58 PM, Davi Duarte wrote:
Hello,
I'm using PL/Python in PostegreSQL 9.0.3 and Python 2.6.5, I want to use
a feature of Python 3, Python have an option to import a module from
future version of Python.
In my case, I want to use the Python 3 division module, because it
returns a
On 03/31/2011 01:08 AM, Mike Orr wrote:
That might be a better solution. I was hoping to use the same pgdump
file for this that I also use for routine offline backup, but maybe
this is such a special case that a separate dump file would be better.
Why don't you post the exact mysqldump/mysql co
On 05/25/2011 03:01 AM, John R Pierce wrote:
On 05/24/11 5:50 PM, Andrej wrote:
Add more RAM? Look at tunables for other processes on
the machine? At the end of the day making the kernel shoot
anything out of despair shouldn't be the done thing.
somehow, 'real' unix has neither a OOMkiller nor
On 02/08/2010 21:14, John R Pierce wrote:
Another factor, if your linux system was using LVM (its the default
storage configuration on many distributions), there's a pretty good
chance the drive mapper is ignoring write barriers, which greatly speeds
up random writes at the expense of reliable co
On 11/08/2010 04:01, Greg Smith wrote:
3. The default configuration settings for PostgreSQL are not optimal
for performance. Can there be a recommended configuration file in the
installation (assuming certain amount of RAM and processor type) ?
This doesn't work because there are many different
On 11/08/2010 17:34, Greg Smith wrote:
The problem here is that the amount of shared memory a system can
allocate is hard to discover any other way than starting the server and
seeing if it works. So doing what you advise will leave the database
unable to start on any system that hasn't gotten th
On 12/08/2010 03:43, Tom Lane wrote:
Marco Colombo writes:
It's a matter of correctness: I see PG as a high
performance database system. Allowing to start it in awfully suboptimal
conditions it's no different from allowing '-00-00' as a date: it
may give you the id
Phoenix Kiula wrote:
Thanks Andrew.
On the server (the DB to be dumped) everything is "UTF8".
On my home server (where I would like to mirror the DB), this is the output:
=# \l
List of databases
Name| Owner | Encoding
---+-+---
pos
Jeff Amiel wrote:
> Ahhh
> *looks at encoding*
>
> Well..they are both the same...BUT...they are set to
> ENCODING = 'SQL_ASCII';
>
> That explains a lotthey should probably be set to Unicode UTF8
> Duh
>
> Any way to change encoding without dumping/restoring database?
You can
admin wrote:
> Sorry folks, a perennial one I'm sure ...
>
> I have read the manual and Googled for a couple of hours but still can't
> connect to PostgreSQL 8.3.4 (the PGDG RPMs running on an up to date
> CentOS 5.2).
>
> I continually get this message:
>
> psql: could not connect to server: No
Scott Marlowe wrote:
> On Wed, Oct 15, 2008 at 10:17 AM, Richard Broersma
> <[EMAIL PROTECTED]> wrote:
>> On Wed, Oct 15, 2008 at 9:03 AM, Reg Me Please <[EMAIL PROTECTED]> wrote:
>>
>>> Both are perfectly right, indeed.
>>> Nonetheless, in my opinion a NATURAL JOIN exploiting the FKs
>>> instead
Tom Lane wrote:
> Andrew Gould writes:
>> To the list: Does pg_dump escape characters that are the same as the
>> delimiter?
>
> Yes. The OP has not actually explained why he needs to pick a
> nondefault delimiter, unless maybe it is that he wants to feed the
> dump to some program that is too
Tom Lane wrote:
> shadrack writes:
>> My basic question is...are php4 and postgresql 8.3 compatible?
>> I'm running Linux Redhat 3.4.6, php4.3.9, and postgresql 8.3. I know,
>> some of those versions are old...its government, and I unfortunately
>> don't have control over the version.
>
> Er ...
Scott Marlowe wrote:
> On Fri, Mar 6, 2009 at 2:22 PM, Ben Chobot wrote:
>> On Fri, 6 Mar 2009, Greg Smith wrote:
>>
>>> On Fri, 6 Mar 2009, Tom Lane wrote:
>>>
Otherwise you need to reconfigure your drive to not cache writes.
I forget the incantation for that but it's in the PG list a
Tom Lane wrote:
> Marco Colombo writes:
>> And I'm still wondering. The problem with LVM, AFAIK, is missing support
>> for write barriers. Once you disable the write-back cache on the disk,
>> you no longer need write barriers. So I'm missing something, what els
Scott Marlowe wrote:
> On Fri, Mar 13, 2009 at 1:09 PM, Christophe wrote:
>> So, if the software calls fsync, but fsync doesn't actually push the data to
>> the controller, you are still at risk... right?
>
> Ding!
>
I've been doing some googling, now I'm not sure that not supporting barriers
i
Joshua D. Drake wrote:
> On Sat, 2009-03-14 at 05:25 +0100, Marco Colombo wrote:
>> Scott Marlowe wrote:
>
>> Also see:
>> http://lkml.org/lkml/2008/2/26/41
>> but it seems to me that all this discussion is under the assuption that
>> disks have write-ba
Joshua D. Drake wrote:
>
> I understand but disabling cache is not an option for anyone I know. So
> I need to know the other :)
>
> Joshua D. Drake
>
Come on, how many people/organizations do you know who really need 30+ MB/s
sustained write throughtput in the disk subsystem but can't afford a
John R Pierce wrote:
> Stefan Kaltenbrunner wrote:
>> So in my understanding LVM is safe on disks that have write cache
>> disabled or "behave" as one (like a controller with a battery backed
>> cache).
>
> what about drive write caches on battery backed raid controllers? do
> the controllers ens
Greg Smith wrote:
> On Tue, 17 Mar 2009, Marco Colombo wrote:
>
>> If LVM/dm is lying about fsync(), all this is moot. There's no point
>> talking about disk caches.
>
> I decided to run some tests to see what's going on there, and it looks
> like some o
Ron Mayer wrote:
> Greg Smith wrote:
>> There are some known limitations to Linux fsync that I remain somewhat
>> concerned about, independantly of LVM, like "ext3 fsync() only does a
>> journal commit when the inode has changed" (see
>> http://kerneltrap.org/mailarchive/linux-kernel/2008/2/26/9905
Greg Smith wrote:
> On Wed, 18 Mar 2009, Marco Colombo wrote:
>
>> If you fsync() after each write you want ordered, there can't be any
>> "subsequent I/O" (unless there are many different processes
>> cuncurrently writing to the file w/o synchronizatio
Ron Mayer wrote:
> Marco Colombo wrote:
>> Ron Mayer wrote:
>>> Greg Smith wrote:
>>>> There are some known limitations to Linux fsync that I remain somewhat
>>>> concerned about, independantly of LVM, like "ext3 fsync() only does a
>>>>
Martijn van Oosterhout wrote:
> Generally PG uses O_SYNC on open, so it's only one system call, not
> two. And the file it's writing to is generally preallocated (not
> always though).
It has to wait for I/O completion on write(), then, it has to go to
sleep. If two different processes do a write(
Martijn van Oosterhout wrote:
> True, but the relative wakeup order of two different processes is not
> important since by definition they are working on different
> transactions. As long as the WAL writes for a single transaction (in a
> single process) are not reordered you're fine.
I'm not tota
Ron Mayer wrote:
> Marco Colombo wrote:
>> Yes, but we knew it already, didn't we? It's always been like
>> that, with IDE disks and write-back cache enabled, fsync just
>> waits for the disk reporting completion and disks lie about
>
> I've looked ha
Markus Wanner wrote:
> Hi,
>
> Martijn van Oosterhout wrote:
>> And fsync better do what you're asking
>> (how fast is just a performance issue, just as long as it's done).
>
> Where are we on this issue? I've read all of this thread and the one on
> the lvm-linux mailing list as well, but still
linnewbie wrote:
> On Apr 9, 1:00 pm, st...@blighty.com (Steve Atkins) wrote:
>> On Apr 9, 2009, at 9:27 AM, linnewbie wrote:
>>
>>> Hi all,
>>> I have stored HTML in a text field that I subsequently render on the
>>> web. However when I retrieve and render this data on the web I am
>>> getting t
advantage of commercial software is psychological: it's much easier
to convince your boss pay 50,000$ in hardware if your company is
already paying similar figures in software. That is, companies are
more willing to pay $100,000 50% hardware and 50% software than
$50,000 100% hardware, to solve
too
old. Please note that as far as PostgreSQL is concerned, CPU usage
is more important than raw speed in tests, IMHO. And I bet both the
filesystems have improved since then.
Now I wonder, is tab-completion faster in Oracle? B-)
.TM.
--
/ / /
/ /
den
of making technologies available to as many non-guru users as possible
is on distribution makers. If Mr. Shirky wants to set a date, and
say "before that" and "after that", it's the day open source
distrubutions hit the masses. Ce
e same
connection method you're using with pgadmin3, and run it under the same
user you run pgadmin3 with. E.g.:
psql -h localhost -p 5432 -U postgres mydb
see psql manual for details.
If you successfully get to 5), it's likely it's a pgadmin3 problem.
.TM.
--
_
is not on /etc/passwd, only in LDAP.
So, we still have a mystery :-(
Does Debian include and activate SELinux?
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / /
ient library, or buy a commercial licence from them. Why?
With PostgreSQL you don't have to thing about these issues. A big win.
.TM.
--
____/ ____/ /
/ / / Marco Colombo
___/ ___ / / Technic
#1, May 7 2004, 10:31:40)
[GCC 3.3.3 20040412 (Red Hat Linux 3.3.3-7)]
running:
print 1
print 2
1
2
end
running:
print 1^M
print 2^M
File "", line 1
print 1^M
^
SyntaxError: invalid syntax
end
Finalized.
I bet on windows the first program fails and the second is ok
at the end of a line that I can think of). But requiring the
input being text is not 'bizarre' at all.
The issue about text representation affects _any_ application.
Treating text as binary data is plain wrong, IMHO, and will always
lead to problems.
.TM.
--
__
ess the recommended way to document a function (or class
or module or whatever). See PEP 257 for more examples:
http://www.python.org/peps/pep-0257.html
So, to answer to your question, newlines are more than allowed in
string literals.
.TM.
--
/ / /
/ / /
ussing until we have some real world
data. I can't compile on windows, so I'll have to wait someone else
to do that. I'm basing my opinions on Python documentation only.
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / /
On Wed, 16 Mar 2005, Michael Fuhr wrote:
On Wed, Mar 16, 2005 at 01:46:23PM +0100, Marco Colombo wrote:
It seems python documentation is plain wrong, or I'm not able to
read it at all:
http://docs.python.org/ref/physical.html
"A physical line ends in whatever the current platform'
On Wed, 16 Mar 2005, Michael Fuhr wrote:
On Wed, Mar 16, 2005 at 04:17:51PM +0100, Marco Colombo wrote:
aprogram = "x = 1\nprint x\n";
printf(aprogram);
PyRun_SimpleString(aprogram);
See? THIS program requires compile-time or run-time checks. You
can't run it on
On Wed, 16 Mar 2005, Michael Fuhr wrote:
[I've changed the Subject back to the thread that started this
discussion.]
On Wed, Mar 16, 2005 at 05:52:02PM +0100, Marco Colombo wrote:
I'm against to any on-the-fly conversion, now.
I don't like the idea of PostgreSQL accepting input in
filesystem.
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / / ESI s.r.l.
_/ _/ _/ [EMAIL PROTECTED]
---(
On Thu, 17 Mar 2005, Tom Lane wrote:
Martijn van Oosterhout writes:
On Thu, Mar 17, 2005 at 01:03:36PM +0100, Marco Colombo wrote:
OMG! It's indenting the funtion body. I think you can't do that
w/o being syntax-aware. I'm not familiar with the code, why is it
adding a 'def&#x
es not require source munging. I'm aiming at removing the
need for extra indentation. The \r\n thing is another beast, and I'm
not sure it belongs to the same place in our code.
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / /
e where the "pass" node is in the first tree.
We should get a parse tree ready for compilation.
I wish I could "push" the right tokens in the right places,
but it seems it's not possible.
Stay tuned.
.TM.
--
/ / /
/ / /
On Fri, 18 Mar 2005, Tom Lane wrote:
Marco Colombo <[EMAIL PROTECTED]> writes:
Right now I'm parsing the string first, changing the resulting
parse tree adding missing nodes (def, INDENT, DEINDENT) and
then compiling it.
Hmmm ... is this really going to be simpler or more robust than
ms are \n separated,
no matter what platform the server runs on. Client applications just need
to conply, which is what I suggested some time ago. I'm glad to hear
there's nothing to change on the server side.
.TM.
--
/ / /
/ /
and let the users or the application
handle the conversion.
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / / ESI s.r.l.
_/ _/ _/
message
contains a NL or a CR alone.
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / / ESI s.r.l.
_/ _/ _/ [EMAIL PROTECTED]
meters):", curs.fetchone()[0]
-- >8 CUT HERE
This is the output (on Linux):
Comparisons:
q1 == q2 q1 == q3 q2 == q3
False False False
Running tests...
Test 1 (string literal): 0
Test 2 (Python escapes): 1
Test 3 (PG escapes): 1
Te
On Tue, 29 Mar 2005, Marco Colombo wrote:
# escapes (expanded by PostgreSQL)
q3 = r"select count(f1) from test1 where f1 = 'this is a multi line
string\r\nline2\r\nline3\r\n'"
curs.execute(q3)
^^
This line (no. 28) is useless (but harmless), please ignore
LISP module ever existed.)
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / / ESI s.r.l.
_/ _/ _/ [EMAIL PROTECTED]
---(end of broadcast)--
any other way to access PostgreSQL than
sockets, so you need those at least. There's no standalone library
you can link to in order to access database files, AFAIK.
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ /
's not,
I'm replying to Scott. I've realized the reply was private only
just before sending this out.]
> > On Wed, 2005-04-20 at 12:07, Marco Colombo wrote:
> > > On Wed, 2005-04-20 at 11:18 -0500, Scott Marlowe wrote:
> > >
> > > Generally XFS and
onsensus for the
pgsql lists. There's _no_ general consensus. There's _no_ clear winner.
And if you do want a winner anyway, it's ext3, so far.
This "ext3 is not good as XFS as JFS" is a recurring subject, as
long as "ext3 is buggy". _Every single time_ I&
o affects ccNUMA, of course, I'm not saying NUMA avoids this in
any way. But it's a price _both_ have to pay, moving their numbers
towards the worst case anyway (which makes the worst case not so worse).
.TM.
--
/ / /
/ / /
ent, type:
rpm2cpio postgresql-7.4.7-3.FC3.1.src.rpm | cpio -itv
See rpmbuild(8) manual page for details on how to build binary RPMs from
the source one.
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / /
In your case, by choosing (name, address) as the primary key, you're
saying 'I need to know both the name and the address to be able to
retrieve a datum in the table'. This implies that if you have partial
knowledge (you don't know the address), you can
ans to
the extent needed by this specification.
It's up to the module implementation to use real SQL cursors when
possible. AFAIK, it's not done automagically for PostgreSQL.
In practice, DBI cursor objects and SQL cursors have little in common
in th
abases that allow you to send SQL statements (any
kind, not only SELECTs) only in a cursor (either implicit or explicit),
hence the name for the cursor object.
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / / Technical Manager
weird authentication mechanism, try and
consider whether you really need persistent connections. Search the
lists, it has been discussed in the past. I remember of this thread:
http://archives.postgresql.org/pgsql-php/2005-02/msg9.php
There may be others, too.
.TM.
--
/ __
On Mon, 2005-05-02 at 17:32 +0200, Hannes Dorbath wrote:
> On 02.05.2005 16:41, Marco Colombo wrote:
>
> > Have you measured the real gain in using persistent connections at all?
>
> As simple as possible:
>
> require_once('Benchmark/Timer.php');
> $tim
console window (IDLE I think).
You should be able to find some examples via Google.
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / / ESI s.r.l.
_/ _/ _/ [EMAIL PROTECTED]
---(end o
important part of it.
Check out some performance tuning pages, you may need to adjust some OS
and PostgreSQL configuration parameters to allow and effectively handle
100+ connections (shared buffers come to mind). I believe the same is
true for MySQL.
.TM.
--
/ / /
On Fri, 2005-06-03 at 08:43 -0400, Christopher Browne wrote:
> After takin a swig o' Arrakan spice grog, [EMAIL PROTECTED] (Marco Colombo)
> belched out:
> > The hardware seems to be the bottleneck. Try improving the performance
> > of your disk systems. It's very u
ta (maybe you don't care much about
that), _and_ the key. You don't want them to be able to sign stuff or
impersonate your servers with it.
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / / Technical Manager
postgres50 Jan 15 21:15 akey
in any Unix system? Only "postgres" and "root" can read it.
How about backups? Does the backup process (I assume it runs as
administrator) store the key in cleartext?
.TM.
--
/ / /
/ / /
he ability to use some more buzzwords). The level of
protection is just the same of a Unix file with the right permissions.
The key point here is that both the 'postgres' user and 'administrator'
have _transparent_ access to the file contents. No password required.
.TM.
--
space (possibly in a locked area). It may
be available to root ("debugging" the server), the user or the process
itself of course, if "they" manage to execute arbitrary code. There's
not way to make it 100% safe.
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / / T
On Thu, 2005-06-09 at 05:21 -0700, Changyu Dong wrote:
> --- Marco Colombo <[EMAIL PROTECTED]> wrote:
>
> > As long as the 'postgres' user has access to it w/o
> > typing any password,
> > that's only a detail. Unless someone physically
> > stea
postmaster? All the SSL thing should happen before the fork I think. Is
the Windows model different? Do backends handle SSL negotiation?
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/
ntain function pointers,
> which are not guaranteed to point to the same thing in the child.
Ouch, I see the problem. You do need to pass the unencrypted key around
then, assuming openssl supports such a thing. Now I also see it's
useless to setup the op
e all restrictions would be overriden, right ?
No, because pg_dumpall doesn't override any restriction.
Of course, if someone puts his hands on _your_ backups (made with full
permissions), he can access everything, unless you encrypted it.
.TM.
--
/ / /
/ / /
hammer or a RDBMS. When the tool is aimed mostly at such
tasks, there's little need to make it too newbie-friendly.
.TM.
--
/ / /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / / ESI s.r.l.
_/ _/ _/ [EMAIL
ive tasks and so on. There should be no need to use them in
"normal" queries.
Unless you're coding quick and dirty hacks when you really know what
you're doing but don't care about the correctness of your design, of
course.
.TM.
--
__
ious solution (a normal PostGreSQL server, with a standard
filesystem) does not work/fit. Then you choose a solution.
>
> Regards,
> Vinita Bansal
.TM.
--
/ / /
/ / / Marco Colombo
___/
nough. Consider distributing the load on
different servers (you'll need a multi-master solution for that, search
the archives), that is, upgrade your hardware in number not in size.
I hope it helps,
.TM.
--
/ / /
/ / / Marco Colombo
___/
MFS, even if not 100% safe.
Face it, if you want 100% safety (loosing nothing in case of power
failure), you need to synchronously write to _some_ disk platter. Where
this disk is attached to, it's a matter of convenience. _If_ disk write
throughput _is_ the problem, you have to f
mp; pgbench:
>
>
> http://www.canaan.co.il/users/miki/stats/stats.html
>
>
> Cheers
Have you tried data=journal / data=ordered / data=writeback mount
options for ext3? If so, did they make any difference?
.TM.
--
/ / /
/
uot; (or time) between
1979-12-31 and 1980-01-01. It's much like trying to store sqrt(-1) into
a real. I hardly can imagine how MySQL manages to store that (the
1980-01-00, I mean).
.TM.
--
/ / /
/ / / Marco Colombo
_
Ashish Karalkar wrote:
> Hello All,
>
> Can anybody please point me to Advantages and Disadvantages of using view
>
>
> With Regards
> Ashish...
Well, IMHO views are part of the "business logic" and not of the data
model. You can also think of them as an API to access the data from
applications
Hello,
I have a few questions on backuping a PostgreSQL server (lets say
anything 8.x.x). I've read "Continuous Archiving and Point-In-Time
Recovery (PITR)" in the manual I'm still missing something...well
actually I think I don't but I've been debating on this with a friend
for a while, and there'
Tom Lane wrote:
> No. You have to have an actual archive_command script copying the WAL
> segments somewhere else when told to. An asynchronous copy of the xlog
> directory will be nothing but garbage, because we recycle WAL segments
> as fast as we can (ie, as soon as the archive_command claims
Richard Huxton wrote:
> It calls archive_command on the just-filled one.
Good to know, thanks. I think I'll experiment a bit with
archive_command. My point was that since I know (or better assume) that
old segments are going to stay in my pg_xlog for *days* before getting
recycled, just copying th
Tom Lane wrote:
> Marco Colombo <[EMAIL PROTECTED]> writes:
>> Good to know, thanks. I think I'll experiment a bit with
>> archive_command. My point was that since I know (or better assume) that
>> old segments are going to stay in my pg_xlog for *days* before gett
1 - 100 of 146 matches
Mail list logo
