[GENERAL] Installing postgis-pg90-setup-1.5.2-3 on windows after installing postgresql-9.0.1-1-windows_x64 errors off

2010-11-01 Thread John Mitchell
Hi,

Installing postgis-pg90-setup-1.5.2-3 on windows after installing
postgresql-9.0.1-1-windows_x64 errors off (see below error).  I believe that
postgres is a 64 bit application and postgis is a 32 bit application so I
don't know if that is the reason why it errors off.

*psql:C:/Program
Files/PostgreSQL/9.0/share/contrib/postgis-1.5/postgis.sql:58: ERROR:  could
not load library C:/Program Files/PostgreSQL/9.0/lib/postgis-1.5.dll: %1
is not a valid Win32 application.
*
John



-- 
John J. Mitchell


Re: [GENERAL] What locking mechanism is used for database backup and restore and Master-Slave Replication?

2010-01-22 Thread John Mitchell
When is the new version of postgres (8.5) scheduled to be released as the
latest stable version?

Thanks,

John

2010/1/21 Grzegorz Jaśkiewicz gryz...@gmail.com

 depends on what sort of replication you are going to use really.
 Most are based on triggers. So they have a bit more impact on
 performance. As far as locking goes, postgresql is very conservative
 with locks, ie - it won't abuse them, unlike for instance mysql.
 So I don't know whether you are just worried about performance in
 general, or locking in particular. But impact of likes of slony isn't
 that big, but obviously once the new version is out - it will be even
 less of a problem, since postgresql already produces transactional log
 for recovering, and pretty much the same log is going to be used for
 replication.


 2010/1/21 John Mitchell mitchellj...@gmail.com:
  So am I to presume that the current stable version of postgres (before
 8.5)
  does require extra locking?
 
  John
 
  2010/1/21 Grzegorz Jaśkiewicz gryz...@gmail.com
 
  On Thu, Jan 21, 2010 at 1:12 PM, John Mitchell mitchellj...@gmail.com
  wrote:
   Hi,
  
   In reading the documentation it states that the SQL dump backup does
 not
   block other operations on the database while it is working.
  yes, pg_dump opens serializable transaction thus guarantees data to be
  the exact snapshot (as opposed to the default isolation level, which
  is called 'read commited' not without reason).
  
   I presume that while a restore is occurring that no reads or updates
 are
   allowed against the restored database.
  nope, what restoring does, is just running all the commands in the
  pg_dump (whether it is binary or textual). So as soon as the database
  is created, it is treated just as any connection, thus allows you to
  connect and use it.
 
 
   What locking mechanism is used for Master-Slave Replication?
 
  master slave that's introduced in what's to be 9.0 (aka 8.5), uses WAL
  shipping. So it doesn't require any extra locking.
 
 
 
  --
  GJ
 
 
 
  --
  John J. Mitchell
 



 --
 GJ




-- 
John J. Mitchell


[GENERAL] What locking mechanism is used for database backup and restore and Master-Slave Replication?

2010-01-21 Thread John Mitchell
Hi,

In reading the documentation it states that the SQL dump backup does not
block other operations on the database while it is working.

I presume that while a restore is occurring that no reads or updates are
allowed against the restored database.

What locking mechanism is used for Master-Slave Replication?

Thanks,

John J. Mitchell


Re: [GENERAL] What locking mechanism is used for database backup and restore and Master-Slave Replication?

2010-01-21 Thread John Mitchell
So am I to presume that the current stable version of postgres (before 8.5)
does require extra locking?

John

2010/1/21 Grzegorz Jaśkiewicz gryz...@gmail.com

 On Thu, Jan 21, 2010 at 1:12 PM, John Mitchell mitchellj...@gmail.com
 wrote:
  Hi,
 
  In reading the documentation it states that the SQL dump backup does not
  block other operations on the database while it is working.
 yes, pg_dump opens serializable transaction thus guarantees data to be
 the exact snapshot (as opposed to the default isolation level, which
 is called 'read commited' not without reason).
 
  I presume that while a restore is occurring that no reads or updates are
  allowed against the restored database.
 nope, what restoring does, is just running all the commands in the
 pg_dump (whether it is binary or textual). So as soon as the database
 is created, it is treated just as any connection, thus allows you to
 connect and use it.


  What locking mechanism is used for Master-Slave Replication?

 master slave that's introduced in what's to be 9.0 (aka 8.5), uses WAL
 shipping. So it doesn't require any extra locking.



 --
 GJ




-- 
John J. Mitchell


[GENERAL] When running pgsql2shp it truncates fields that are over 10 characters. How can I prevent this from occurring?

2009-11-15 Thread John Mitchell
When running pgsql2shp it truncates fields that are over 10 characters.  How
can I prevent this from occurring?

John

-- 
John J. Mitchell


[GENERAL] How do I connect postgres table structures and view structures to an existing svn repository?

2007-08-01 Thread John Mitchell
Hi,

How do I connect postgres table structures and view structures to an
existing svn repository?

Thanks,

-- 
John J. Mitchell


Re: [GENERAL] How do I connect postgres table structures and view structures to an existing svn repository?

2007-08-01 Thread John Mitchell
Hi,

I am trying to store schema definitions in version-control which I can do by
saving the definition and then  importing  into svn, but I  would like  it
to be automatic , so that when an update occurs to a table or view within
postgres then that table or view is flagged within svn.  This would be
similar to what I currently do with source code that I have for a web app
within  eclipse.

On 8/1/07, Tino Wildenhain [EMAIL PROTECTED] wrote:

 John Mitchell schrieb:
  Hi,
 
  How do I connect postgres table structures and view structures to an
  existing svn repository?

 Please elaborate: what do you mean with connect?
 If you want to version control your DDL, people
 use pgdump to create individual dumps (as sql
 text files) and just add/commit them to the
 repository.

 Regards
 Tino




-- 
John J. Mitchell