On Mon, Aug 12, 2013 at 04:41:48PM -0400, David F. Skoll wrote:
On Mon, 12 Aug 2013 16:05:04 -0400
Bruce Momjian br...@momjian.us wrote:
On Mon, Aug 12, 2013 at 08:33:04AM -0700, Joshua D. Drake wrote:
Put the pg_xlog on spindles, they are more than fast enough and
won't eat up
On Fri, Aug 9, 2013 at 10:20:13AM +0200, Jan Lentfer wrote:
On Thu, 8 Aug 2013 21:36:35 -0400, Bruce Momjian wrote:
On Tue, Jul 16, 2013 at 11:30:54AM -0500, Nestor A. Diaz wrote:
Hello People, In reference to my last post , my question is: It is
possible to recover
not possible and I want to
confirm that, is it possible in 9.1 ?
I am confused. You did recovery, and then you want to do more WAL
files past your stop point?
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's
schema performance,
though. You might need to just test it.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin
.
Also, is there any hard limit on number of schemas and tables that can be
present in one postgres database?
Not really, unless you start getting into the 100M count.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
statistics (Bruce Momjian)
This reduces the time needed to generate minimal cluster statistics
after an upgrade.
It runs with a 1/10/default statistics target.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
that, but since 9.2 creates an incremental
statistics build script, I need someone to say that is too slow before I
code up something more complex.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible
about this at PGCon 2013 and I plan to
work on this for 9.4.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin
catalog version
when using tablespaces
Why 9.0.4 and 9.1.3 are same catalog version?
Is there a workarround for this problem, I would like to avoid
using a dmp.
You did something wrong as those versions use different catalog
versions.
--
Bruce Momjian br...@momjian.ushttp
you all the errors but will not affect your cluster. And you can
use safe it on a running instance BTW.
While that is a good suggstion, it would not have found this error
becaues --check does not test the restore of the database schemas.
--
Bruce Momjian br...@momjian.ushttp
they changed their internal format, but I am not sure. There
are various ways of getting help for postgis:
http://postgis.net/support/
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible
On Mon, Jun 17, 2013 at 07:08:03PM -0400, Bruce Momjian wrote:
On Mon, Jun 17, 2013 at 10:54:06AM -0700, jmfox180 wrote:
so i'm running ubuntu 12.04 with pg8.3.2 installed on it, i want to upgrade
to 9.2.4 using the pg_upgrade. i've followed this steps:
1) download postgres9.2.4
2
OK, so your database references '$libdir/liblwgeom', but the file does
not exist in the 9.2.4 lib directory. Odds are it is some Postgres
extension that you need to install in the new cluster.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
the new cluster. If you
don't start the new cluster, you can just delete the new cluster and
restart the unchanged old cluster, thought you have to remove the .old
suffix on the control file.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
. My guess is that
your /usr/local/pgsql9.2.0/data/ isn't really 9.2.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql
guess is that you didn't have many tablespaces or databases, or the
copy time overwhelmed the performance improvement of the parallelism.
I am not surprised you didn't see a big win. Can you test --link
mode?
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
://www.idallen.com/topposting.html
I think in-line commenting or trimming the text above to show just the
part you are responding to is the greatest benefit for bottom posting.
If you are _not_ doing that, there is probably little value to
bottom-posting.
--
Bruce Momjian br...@momjian.ushttp
sentences containing $SUBJECT because the poster can't be
bothered to actually state their topic as part of the sentence? I
usually ignore those too. Oh, and people posting to multiple email
lists.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
no changes take effect.
There settings I tried to change are:
-effective_cache_size
-work_mem
Im using posgres 9.1 on Centos Linux (amazon ec2)
That is quite odd. Can you show us the commands and the postgresql.conf
line you are changing?
--
Bruce Momjian br...@momjian.ushttp
object/tables do you have? I have just patched 9.2 to
improve upgrades for clusters with many objects.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via
On Wed, Nov 7, 2012 at 10:44:12AM -0800, Lonni J Friedman wrote:
On Wed, Nov 7, 2012 at 10:42 AM, Bruce Momjian br...@momjian.us wrote:
On Fri, Oct 19, 2012 at 02:44:05PM -0700, Lonni J Friedman wrote:
Greetings,
I'm in the process of planning for a production upgrade from 9.1.6 to
9.2.x
On Wed, Nov 7, 2012 at 01:06:19PM -0800, Lonni J Friedman wrote:
On Wed, Nov 7, 2012 at 12:59 PM, Bruce Momjian br...@momjian.us wrote:
On Wed, Nov 7, 2012 at 10:44:12AM -0800, Lonni J Friedman wrote:
On Wed, Nov 7, 2012 at 10:42 AM, Bruce Momjian br...@momjian.us wrote:
On Fri, Oct 19
On Wed, Nov 7, 2012 at 01:09:19PM -0800, Lonni J Friedman wrote:
On Wed, Nov 7, 2012 at 1:07 PM, Bruce Momjian br...@momjian.us wrote:
On Wed, Nov 7, 2012 at 01:06:19PM -0800, Lonni J Friedman wrote:
On Wed, Nov 7, 2012 at 12:59 PM, Bruce Momjian br...@momjian.us wrote:
On Wed, Nov 7
and find
out why the thread testing failed. If you don't need client-level
threads, you should be fine.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via
://www.postgresql.org/support/versioning/
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes
clusters
that have the mismatch and let me know. It might be something that
isn't in the old cluster, or not in the new cluster.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything
know why those would be different, and in fact, because we have never
hit this, there isn't even any debug output that shows the source of the
difference.
If I send you a patch can you compile it and send back the debug output
it produces?
--
Bruce Momjian br...@momjian.ushttp
files and email the result to us; it
should show the mismatch. I am not sure if the dumps will output the
objects in the same order, it might.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible
.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http
just saying 2 billlion is better.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes
On Thu, Sep 13, 2012 at 11:36:56PM +0200, Christian Ullrich wrote:
* Bruce Momjian wrote:
On Thu, Sep 13, 2012 at 02:15:00PM +0200, Christian Ullrich wrote:
c:\Datenpath
PATH=c:\windows;c:\windows\system32;c:\Program Files\PostgreSQL\9.2\bin
c:\Datenpg_upgrade --old-bindir=c:\Program
at the SQL queries that look in the pg_proc
table for such entries.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin
just need to have a valid data directory and binaries --- you don't
need source.
---
Thanks again.
On Wed, Sep 12, 2012 at 1:17 AM, Bruce Momjian br...@momjian.us wrote:
On Tue, Sep 11, 2012 at 04:15:31PM +0300
after running pg_upgrade?
You will need to have all plug-in stuff installed in the new
cluster before running pg_upgrade. You should then be able to run
pg_upgrade and all your postgis data will be migrated.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
On Mon, Sep 10, 2012 at 12:06:10PM -0500, Kevin Grittner wrote:
Craig James cja...@emolecules.com wrote:
Sergey Konoplev gray...@gmail.com wrote:
Bruce Momjian br...@momjian.us wrote:
On Thu, Sep 6, 2012 at 05:55:05PM -0500, Antoine Guidi wrote:
Is it possible to do a pg_upgrade from
to stop the server,
install the binaries, and restart the server.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin
of an edge case that I should come up with some solution or work-around
on my own? Thanks,
Late reply, but I don't see any way we could fix this easily.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible
, are the n_live_tup and n_dead_tup values kept somewhere
internally, apart pg_stat_all_tables?
No. pg_reset_stats() will affect autovacuum, usually in a bad way.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible
postmaster.pid must be deleted from the copy to avoid an error message from
pg_upgrade.)
OK, we already document the problems with postmaster.pid and rsync in
the backup section, so I added a mention of that to the pg_upgrade docs,
and backpatched that to 9.2.
--
Bruce Momjian br...@momjian.us
is accustomed to run on.
I think it would only really be an issue if PG's block size weren't a
multiple of the filesystem block.
I have heard about performance issues when the virtual machine block
size isn't aligned with the host OS block size.
--
Bruce Momjian br...@momjian.ushttp
it handy so that I may want to
refer back whenever I need.
Thanks once again for that great explanation.
Agreed. That was pretty amazing!
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible
-hackers/2008-01/msg00846.php
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your
basically
forces it to do a tcp connection to the local database --- the default
is to do a unix-domain socket/local connection to the database.
Glad you finally got it working.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http
that the
old index will be used as is?
That is quite odd. I have no idea what would cause that.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql
:48 0:10 /bin/sh
/usr/lib/postgresql/9.1/bin/pg_config --pkglibdir
so far I have broken off after about 5 minutes. Has anybody seen this
behaviour before?
Nope. I remember someone else complaining that pg_controldata or
pg_config was stuck, but I couldn't figure out why.
--
Bruce
Bernhard Rohrer wrote:
On 08/09/11 20:49, Bruce Momjian wrote:
Bernhard Rohrer wrote:
Hiya
running lucid 64 bit. When I try to start pg_upgrade I get the following
output:
postgres@newcollab:/tmp$ /usr/lib/postgresql/9.1/bin/pg_upgrade -b
/usr/lib/postgresql/9.0/bin -B /usr/lib
running and never
returns a result.
There are no real processing loops in pg_config so I am confused what
could be happening --- I would look at some kind of operating system
problem.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http
@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql
Krajmalnik wrote:
Fuji Masao
Hiroshi Saito
Satoshi Nagayasu
Tatsuo Ishii
This information came via Magnus and Dave Page, mainly via Twitter, I
think.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http
Robert Treat wrote:
On Thu, Mar 10, 2011 at 1:30 PM, Bruce Momjian br...@momjian.us wrote:
Mark Johnson wrote:
export PGPORT1=5432
export PGPORT2=5432
export PGDATA1=/pgdata1/test
export PGDATA2=/pgdata1/test
export PGBIN1=/pghome/9.0.2/bin
export PGBIN2=/pghome/9.0.3/bin
ISTM
Gilberto Castillo Mart?nez wrote:
El jue, 10-03-2011 a las 15:33 -0500, Bruce Momjian escribi?:
Dyonisius Visser wrote:
On 10 March 2011 21:03, Bruce Momjian br...@momjian.us wrote:
OK, let's skip documenting this then. ?They can already do this via
pg_hba.conf
attislocal = false
WHERE attname = 'write_uid'
AND attrelid = 'ir_act_url'::pg_catalog.regclass;
-- For binary upgrade, set up inheritance this way.
*24606: ALTER TABLE ONLY ir_act_url INHERIT ir_actions;*
so it comes from the catalog!
Thanks
Bernhard
On 24/02/11 15:10, Bruce Momjian
are
different. I also assume env. variables are allowed and you are not opening
other windows/sessions.
-Mark
You have shown a lot of text above, but not the error message you got.
Can I see that please?
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
would someone listen only on IPv4 addresses?
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make
IPv6, and whether there is an IPv4-only syntax.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org
this via
pg_hba.conf.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your
Dyonisius Visser wrote:
On 10 March 2011 21:03, Bruce Momjian br...@momjian.us wrote:
OK, let's skip documenting this then. ?They can already do this via
pg_hba.conf.
Restricting access via pg_hba.conf is something else than listening
(or not) on sockets...
FYI, the listen_addresses
Gilberto Castillo Mart?nez wrote:
El jue, 10-03-2011 a las 15:33 -0500, Bruce Momjian escribi?:
Dyonisius Visser wrote:
On 10 March 2011 21:03, Bruce Momjian br...@momjian.us wrote:
OK, let's skip documenting this then. ?They can already do this via
pg_hba.conf
, a --schema-only pg_dump is a small file, or
should be.
---
thanks
B original message- From: Bruce
Momjian To: Bruce Momjian CC: Bernhard Rohrer grayl...@sm-wg.net
, Bernhard Schrader
-admin
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http
Bruce Momjian wrote:
Bernhard Rohrer wrote:
Thanks that worked. :)
After this and some more entertainment we are now here:
Restoring database schema to new cluster
psql:/usr/lib/postgresql/9.0/bin/pg_upgrade_dump_db.sql:24606: ERROR:
column name in child table must be marked
Webb, John wrote:
What are the steps and other considerations for setting up Postgres to
use SSL?
I have to set this up for a Postgres 8.2 database.
Read our documentation --- it is very detailed.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
?
Will a DAS work? Or is replication the best approach?
The last section of this documentation page talks about NFS usage:
http://www.postgresql.org/docs/9.0/static/creating-cluster.html
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
does the pg_upgrade script doesn't see that
utf8 and UTF-8 are the same? Is it just a string compare?
Yes, just a string compare.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything
should work fine.
My initial reaction is that something is wrong with your system, either
the I/O or the way it is being shutdown by the script. I would start to
look in the script and do some pg_ctl tests starting/stopping the
server.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
for super-users. If the system is not
shutting down, that should signal to the user that they have not locked
down the system properly. We would not want someone to connect during
pg_upgrade processing, and doing -m fast is not going to help with that.
--
Bruce Momjian br...@momjian.ushttp
Bernhard Schrader wrote:
Am Donnerstag, den 27.01.2011, 12:09 -0500 schrieb Bruce Momjian:
Scott Marlowe wrote:
My initial reaction is that something is wrong with your system, either
the I/O or the way it is being shutdown by the script. ?I would start to
look in the script and do
pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible
, --xlogdir=directory
This option specifies the directory where the
transaction log should be stored.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true
.
These are all very good ideas and I have applied them for 9.1 in the
attached patch. I also found a few libpq titles that needed
capitalization, which is also in the patch. Thanks for the ideas.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
(it seems like it is going to be partial recovery). I
am concerned that even if we are able to clear all those messages by
whatever means the state of the database will be corrupted. Luckily this
True.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
.
Seems you will have to clear those pages too somehow. I have seen it
done with dd.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing
as there is no transaction which would still be able to see them.
Well, single-page vacuums are even more likely to remove old data, and
you can't turn that off. I am working on am MVCC talk for PG/West that
will show how agressive those single-page (HOT and non-HOT) vacuums are.
--
Bruce Momjian br
remote or from a remote machine (where
psql would be local)?
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin
but not by echo |psqlThought
it was strange.
Yeah, that is odd.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
--
Sent via pgsql-admin mailing list (pgsql-admin
.
Yeah, that is odd.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever
the username to each one that supported it; applied patch
attached.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
Index: contrib/pg_upgrade/check.c
tunning etc.
I think you want to post to this list:
http://archives.postgresql.org/pgsql-jobs/
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
--
Sent via pgsql
it be this the
problem ?
Thank you (I hope this is the right list to post this)
Turns out I was missing the user name designation. I am attaching the
patch that fixes this, and a pg_ctl issue on Win32.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
, fdatasync10.999764
write, fsync, 80.696959
Compare file sync methods with 2 8k writes:
(o_dsync unavailable)
write, fdatasync 111.931881
write, fsync, 99.329298
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
hours.
Thanks for the report, and sorry for the problem.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http
Marc G. Fournier wrote:
On Fri, 28 May 2010, Bruce Momjian wrote:
I talked to Dave Page and it seems the pginstaller (non-bitRock) Win32
installers were _not_ moved from their beta holding area to the download
section.
They have just been moved and the URLs are now:
ftp
are not having any problems
with what is essentially identical code.
I would say 'hackers list'.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org
in such a crisis, or help you long before it
becomes a crisis. These kind of problems make everyone look bad.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org
created these tables in the 'template1'
database, and they are getting copied from there everytime you create a
new database. FYI, you can also use another database as the template
database if you wish.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
?
Perhaps this is fixed in 8.3.10.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
or:
ALTER DATABASE ... CONNECTION LIMIT connlimit
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http
server certificate file server.crt: no start line
Sorry about too many questions, but anyone can help me to understand more
about ssl in PostgreSQL?
Have you read the documentation about creating a server key?
http://www.postgresql.org/docs/8.4/static/ssl-tcp.html
--
Bruce Momjian br
of
archive recovery, even when we know it is never present.
so you should not see this when using = PG 9.0.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg
ALIAS, which can now alias any variable, not just dollar
sign variables, e.g. $1.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
--
Sent
in the server logs to see if something if failing there. 9.0 will
have better feedback when pg_stop_backup hangs like that.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com
:
http://archives.postgresql.org/pgsql-announce/2010-02/msg5.php
Koichi, do you have any update on this? I don't see that a new version
has been uploaded, and I also see no mention on the pgfoundry site about
the bug.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-admin mailing
never make such
changes in minor releases.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-admin mailing list (pgsql-admin
).
Will pg_migrator handle this?
No, I do not think it would work to move from 32 to 64-bit because of
alignment changes.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your
?
Or is there a better way? The transaction did roll back.
Sure, that is fine. It doesn't hurt anything. There is also a way to
do it from another session using using pg_cancel_backend().
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http
Devrim G?ND?Z wrote:
-- Start of PGP signed section.
On Mon, 2010-02-01 at 11:12 -0500, Bruce Momjian wrote:
No idea if anyone is building RPMs for it
Of course I'm building ;)
We have pg_migrator 8.4.14 for RHEL/CentOS 4,5 and Fedora 12-i386.
Oh, wow, that's nice.
--
Bruce
, 2010, at 2:00 PM, Bruce Momjian wrote:
Devrim G?ND?Z wrote:
-- Start of PGP signed section.
On Mon, 2010-02-01 at 11:12 -0500, Bruce Momjian wrote:
No idea if anyone is building RPMs for it
Of course I'm building ;)
We have pg_migrator 8.4.14 for RHEL/CentOS 4,5 and Fedora
db online (I am
guessing no...)?
Nope.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-admin mailing list (pgsql-admin
Mark Corner wrote:
All good info...
With respect to RPMs, I was actually referring to postgres84
rpms with non-integer datetime prebuilt.
Oh, I don't think anyone has made any of those, but I can see it
would be useful.
--
Bruce Momjian br...@momjian.ushttp://momjian.us
1 - 100 of 587 matches
Mail list logo
