[GENERAL] Migration to pglister - Before

Greetings, We will be migrating these lists to pglister in the next few minutes. This final email on the old list system is intended to let you know that future emails will have different headers and you will need to adjust your filters. The changes which we expect to be most significant to user

Re: [GENERAL] Migration Query

PAWAN SHARMA schrieb am 08.05.2017 um 17:13: > Does one any having list of bottlenecks and workarounds while migrating data > from Oracle to Postgresql. like what are thing which we can migrate from > Oracle database to Postgresql and what we can't? One thing I have seen regularly is the wrong tr

Re: [GENERAL] Migration Query

On Tue, May 9, 2017 at 1:13 AM, PAWAN SHARMA wrote: > Hi All, > > Does one any having list of bottlenecks and workarounds while migrating > data > from Oracle to Postgresql. like what are thing which we can migrate from > Oracle database to Postgresql and what we can't? > In general you must be

Re: [GENERAL] Migration Query

Does one any having list of bottlenecks and workarounds while migrating data from Oracle to Postgresql. like what are thing which we can migrate from Oracle database to Postgresql and what we can't? Which is the best tool for migration from Oracle to Postgresql? Hi, I like this tool and hav

[GENERAL] Migration Query

Hi All, Does one any having list of bottlenecks and workarounds while migrating data from Oracle to Postgresql. like what are thing which we can migrate from Oracle database to Postgresql and what we can't? Which is the best tool for migration from Oracle to Postgresql? -Pawan

Re: [GENERAL] migration to 9.6 array_accum memory issues

Jiri Sadek writes: > On 27.3.2017 15:46, Tom Lane wrote: >> I think you'll find that 9.6.2 makes this significantly better. >> https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=48a6592da > Actually we did all the testing on 9.6.2-1.pgdg16.04+1 from > http://apt.postgresql.org/pub

Re: [GENERAL] migration to 9.6 array_accum memory issues

On 27.3.2017 15:46, Tom Lane wrote: > Jiri Sadek writes: >> we are in the process of migrating postgresql 9.1 to 9.6 and we >> encounter a memory issues with 9.6 - one of our procedure consumed all >> free memory (~8GB) of the testing server (and make it to swap), there >> was never such problem

Re: [GENERAL] migration to 9.6 array_accum memory issues

Jiri Sadek writes: > we are in the process of migrating postgresql 9.1 to 9.6 and we > encounter a memory issues with 9.6 - one of our procedure consumed all > free memory (~8GB) of the testing server (and make it to swap), there > was never such problem with 9.1. After some testing we found out t

[GENERAL] migration to 9.6 array_accum memory issues

Hi all, we are in the process of migrating postgresql 9.1 to 9.6 and we encounter a memory issues with 9.6 - one of our procedure consumed all free memory (~8GB) of the testing server (and make it to swap), there was never such problem with 9.1. After some testing we found out that it is caused by

Re: [GENERAL] Migration error " invalid byte sequence for encoding "UTF8": 0xff " from mysql 5.5 to postgresql 9.1

John R Pierce wrote: > On 7/4/2014 2:12 AM, sunpeng wrote: >> Thank you, friend, I use --hex-blob : >> mysqldump -v -nt --complete-insert=TRUE --compatible=postgresql >> --default-character-set=utf8 --skip-add-locks --compact >> --no-create-info --skip-quote-names --hex-blob -uroot -p test >> vide

Re: [GENERAL] Migration error " invalid byte sequence for encoding "UTF8": 0xff " from mysql 5.5 to postgresql 9.1

On 7/4/2014 2:12 AM, sunpeng wrote: Thank you, friend, I use --hex-blob : mysqldump -v -nt --complete-insert=TRUE --compatible=postgresql --default-character-set=utf8 --skip-add-locks --compact --no-create-info --skip-quote-names --hex-blob -uroot -p test videorecresult >dbdata.sql to dump m

Re: [GENERAL] Migration error " invalid byte sequence for encoding "UTF8": 0xff " from mysql 5.5 to postgresql 9.1

Thank you, friend, I use --hex-blob : mysqldump -v -nt --complete-insert=TRUE --compatible=postgresql --default-character-set=utf8 --skip-add-locks --compact --no-create-info --skip-quote-names --hex-blob -uroot -p test videorecresult >dbdata.sql to dump mysql data. And replace blob data "0x"

Re: [GENERAL] Migration error " invalid byte sequence for encoding "UTF8": 0xff " from mysql 5.5 to postgresql 9.1

sunpeng wrote: >>> load data to postgresql in cmd(encoding is GBK) is WIN8: >>> >>> psql -h localhost -d test -U postgres < dbdata.sql >>> >>> I got the error: >>> ERROR: invalid byte sequence for encoding "UTF8": 0xff >> If the encoding is GBK then you will get errors (or incorrect >> charact

Re: [GENERAL] Migration error " invalid byte sequence for encoding "UTF8": 0xff " from mysql 5.5 to postgresql 9.1

I‘v changed cmd (in win8) to encoding utf8 through chcp 65001, but error still occurs. And i use the following cmd to dump mysql data: mysql> select Picture from personpicture where id = 'F2931306D1EE44ca82394CD3BC2404D4' into outfile "d:\\1.txt" ; I got the ansi file, and use Ultraedit to see fir

Re: [GENERAL] Migration error " invalid byte sequence for encoding "UTF8": 0xff " from mysql 5.5 to postgresql 9.1

sunpeng wrote: > load data to postgresql in cmd(encoding is GBK) is WIN8: > psql -h localhost  -d test -U postgres <  dbdata.sql > > I got the error: > ERROR:  invalid byte sequence for encoding "UTF8": 0xff If the encoding is GBK then you will get errors (or incorrect characters) if it is read

[GENERAL] Migration error " invalid byte sequence for encoding "UTF8": 0xff " from mysql 5.5 to postgresql 9.1

When I do migration from Mysql to PostgreSQL: firstly dump data from mysql in cmd(encoding is GBK) is WIN8: mysqldump -v -nt --complete-insert=TRUE --compatible=postgresql --default-character-set=utf8 --skip-add-locks --compact --no-create-info --skip-quote-names -uroot -p test >dbdata.sql then lo

Re: [GENERAL] Migration from Symfoware to PostgreSQL-Constructor functions

> how to see list of system tables, functions, view and user defined tables, > functions, views. > > You can get more details from below URL: Extracting META information from PostgreSQL (INFORMATION_SCHEMA) Thanks & Regards Raghu Ram

Re: [GENERAL] Migration from Symfoware to PostgreSQL-Constructor functions

Hi, System tables, views and most of the metadata can be retrieved from these views - http://www.postgresql.org/docs/9.2/static/information-schema.html Regards, Jayadevan On Sun, Aug 4, 2013 at 2:48 PM, sachin kotwal wrote: > Hello > > While migrating small application from Symfoware to Postgr

[GENERAL] Migration from Symfoware to PostgreSQL-Constructor functions

Hello While migrating small application from Symfoware to PostgreSQL. There are some constructor functions in Symfoware. Which I unable to execute in Symfoware database. If anyone knows how to execute constructor functions in Symfoware. how to see list of system tables, functions, view and user d

Re: [GENERAL] Migration from DB2 to PostgreSQL-TIMESTAMP(arg1,arg1)

>I've done something weird: >CREATE OR REPLACE FUNCTION "timestamp"(_date date, _time time) RETURNS timestamp AS $$ >SELECT _date + _time; >$$ LANGUAGE sql; >SELECT "timestamp"('2013-01-01'::date, '12:00:00'::time); Good one. function with above definition is already present in pg_catalog. so n

Re: [GENERAL] Migration from DB2 to PostgreSQL-TIMESTAMP(arg1,arg1)

Using your link http://www.postgresql.org/docs/9.2/static/functions-formatting.html In DB2 when I use following command I am getting output combined date and time i passed to function. #SELECT TIMESTAMP('2013-01-01','12:13:14') FROM SYSIBM.SYSDUMMY1 1 ---

Re: [GENERAL] Migration from DB2 to PostgreSQL-TIMESTAMP(arg1,arg1)

On 6/27/2013 4:51 AM, sachin kotwal wrote: #select timestamp(current_date); try... current_date::timestamptz orcast current_date as timestamptz -- john r pierce 37N 122W somewhere on the middle of the left coast -- Sent via pgsql-general maili

Re: [GENERAL] Migration from DB2 to PostgreSQL-TIMESTAMP(arg1,arg1)

On 2013-06-27 20:43, sachin kotwal wrote: While migrating my application from DB2 to PostgreSQL. I want to migrate TIMESTAMP() function of DB2 into PostgreSQL. Example in DB2: #SELECT TIMESTAMP('2013-01-01','12:13:14') FROM SYSIBM.SYSDUMMY1 1 -- 2013-01-01-12.13.14.

Re: [GENERAL] Migration from DB2 to PostgreSQL-TIMESTAMP(arg1,arg1)

I've done something weird: CREATE OR REPLACE FUNCTION "timestamp"(_date date, _time time) RETURNS timestamp AS $$ SELECT _date + _time; $$ LANGUAGE sql; SELECT "timestamp"('2013-01-01'::date, '12:00:00'::time); It worked, but you will need explict cast and quote the timestamp function name... M

Re: [GENERAL] Migration from DB2 to PostgreSQL-TIMESTAMP(arg1,arg1)

On 27/06/2013 12:51, sachin kotwal wrote: > I have done some more try as follows: > > #select timestamp(current_date); > ERROR: syntax error at or near "current_date" at character 18 > STATEMENT: select timestamp(current_date); > ERROR: syntax error at or near "current_date" > LINE 1: select ti

Re: [GENERAL] Migration from DB2 to PostgreSQL-TIMESTAMP(arg1,arg1)

I have done some more try as follows: #select timestamp(current_date); ERROR: syntax error at or near "current_date" at character 18 STATEMENT: select timestamp(current_date); ERROR: syntax error at or near "current_date" LINE 1: select timestamp(current_date); =

[GENERAL] Migration from DB2 to PostgreSQL-TIMESTAMP(arg1,arg1)

While migrating my application from DB2 to PostgreSQL. I want to migrate TIMESTAMP() function of DB2 into PostgreSQL. Example in DB2: #SELECT TIMESTAMP('2013-01-01','12:13:14') FROM SYSIBM.SYSDUMMY1 1 -- 2013-01-01-12.13.14.00 1 record(s)

Re: [GENERAL] Migration from DB2 to PostgreSQL

On 06/21/2013 04:49 PM, Daniel de Oliveira Mantovani wrote: http://wiki.postgresql.org/images/d/d1/DB2UDB-to-PG.pdf On 18 June 2013 05:52, sachin kotwal wrote: Function in DB2: BLOB() Criteria: Size of character string targeted for cast is more than 1GB How can I migrate this function into P

Re: [GENERAL] Migration from DB2 to PostgreSQL

http://wiki.postgresql.org/images/d/d1/DB2UDB-to-PG.pdf On 18 June 2013 05:52, sachin kotwal wrote: > Function in DB2: BLOB() Criteria: Size of character string targeted for cast > is more than 1GB How can I migrate this function into PostgreSQL with above > mention criteria. > __

Re: [GENERAL] Migration from DB2 to PostgreSQL

On Fri, Jun 21, 2013 at 9:40 PM, sachin kotwal wrote: >>as i know each value is limited to 1GB. For larger content use module lo >>http://www.postgresql.org/docs/9.2/static/lo.html > > > I just want to know that like DB2 we can convert other data types into > CLOB/BLOB using function CLOB()/BLOB()

Re: [GENERAL] Migration from DB2 to PostgreSQL

>as i know each value is limited to 1GB. For larger content use module lo >http://www.postgresql.org/docs/9.2/static/lo.html I just want to know that like DB2 we can convert other data types into CLOB/BLOB using function CLOB()/BLOB(). Example: SELECT CLOB('testdata') FROM SYSIBM.SYSDUMMY1 Same

Re: [GENERAL] Migration from DB2 to PostgreSQL

>PostgreSQL has no such capability. Unless you need that and >want to code it yourself, the best solution would be to >write a function that just ignores the third argument. For time being I will write a function that just ignores the third argument. but if we really want to create such funct

Re: [GENERAL] Migration from DB2 to PostgreSQL

On Thu, Jun 20, 2013 at 12:34 PM, Amit Langote wrote: > On Thu, Jun 20, 2013 at 11:10 AM, Chris Angelico wrote: >> On Thu, Jun 20, 2013 at 12:09 PM, Amit Langote >> wrote: >>> Umm, my bad! I almost forgot I could write pure SQL function bodies. >>> Although, why does following happen? (sorry, a

Re: [GENERAL] Migration from DB2 to PostgreSQL

On Thu, Jun 20, 2013 at 11:10 AM, Chris Angelico wrote: > On Thu, Jun 20, 2013 at 12:09 PM, Amit Langote > wrote: >> Umm, my bad! I almost forgot I could write pure SQL function bodies. >> Although, why does following happen? (sorry, a 8.4.2 installation) : >> >> postgres=# create or replace fun

Re: [GENERAL] Migration from DB2 to PostgreSQL

On Thu, Jun 20, 2013 at 12:09 PM, Amit Langote wrote: > Umm, my bad! I almost forgot I could write pure SQL function bodies. > Although, why does following happen? (sorry, a 8.4.2 installation) : > > postgres=# create or replace function gt(n int, m int) returns boolean > as 'select n>m' language

Re: [GENERAL] Migration from DB2 to PostgreSQL

On Thu, Jun 20, 2013 at 10:54 AM, Chris Angelico wrote: > On Thu, Jun 20, 2013 at 11:35 AM, Amit Langote > wrote: >> On Thu, Jun 20, 2013 at 10:27 AM, Chris Angelico wrote: >>> If your wrapper function is written in SQL and is trivial (eg ignore >>> the third parameter and pass the other two on

Re: [GENERAL] Migration from DB2 to PostgreSQL

On Thu, Jun 20, 2013 at 11:35 AM, Amit Langote wrote: > On Thu, Jun 20, 2013 at 10:27 AM, Chris Angelico wrote: >> If your wrapper function is written in SQL and is trivial (eg ignore >> the third parameter and pass the other two on), the planner should be >> able to optimize right through it. Be

Re: [GENERAL] Migration from DB2 to PostgreSQL

Hi, On Thu, Jun 20, 2013 at 10:27 AM, Chris Angelico wrote: > On Thu, Jun 20, 2013 at 11:10 AM, Amit Langote > wrote: >> If this particular function is to be used repeatedly in a single >> query, would the cost of having a wrapper function around the original >> function be too large? For examp

Re: [GENERAL] Migration from DB2 to PostgreSQL

On Thu, Jun 20, 2013 at 11:10 AM, Amit Langote wrote: > If this particular function is to be used repeatedly in a single > query, would the cost of having a wrapper function around the original > function be too large? For example, if this function appears in a > WHERE clause against a table conta

Re: [GENERAL] Migration from DB2 to PostgreSQL

On Wed, Jun 19, 2013 at 6:00 PM, Albe Laurenz wrote: > sachin kotwal wrote: >> While migrating my application from DB2 to PostgreSQL. >> >> I want to migrate following functions in PostgreSQL. >> >> TO_CHAR() in DB2 which can take three arguments as follows: >> >> SELECT TO_CHAR(CURRENT_DATE,'

Re: [GENERAL] Migration from DB2 to PostgreSQL-ROLLUP()

On Wed, Jun 19, 2013 at 3:56 AM, sachin kotwal wrote: > While migrating my application from DB2 to PostgreSQL. > > I want to migrate ROLLUP() function in PostgreSQL. > > Example: > SELECT WEEK(SALES_DATE) AS WEEK, > DAYOFWEEK(SALES_DATE) AS DAY_WEEK, > SUM(SALES) AS UNITS_SOLD

Re: [GENERAL] Migration from DB2 to PostgreSQL-ROLLUP()

Hello 2013/6/19 sachin kotwal : > While migrating my application from DB2 to PostgreSQL. > > I want to migrate ROLLUP() function in PostgreSQL. > > Example: > SELECT WEEK(SALES_DATE) AS WEEK, > DAYOFWEEK(SALES_DATE) AS DAY_WEEK, > SUM(SALES) AS UNITS_SOLD > FROM SALES > GRO

Re: [GENERAL] Migration from DB2 to PostgreSQL

sachin kotwal wrote: > While migrating my application from DB2 to PostgreSQL. > > I want to migrate following functions in PostgreSQL. > > TO_CHAR() in DB2 which can take three arguments as follows: > > SELECT TO_CHAR(CURRENT_DATE,'-MM-DD',112.50) FROM SYSIBM.SYSDUMMY1 > > I am not sure wha

[GENERAL] Migration from DB2 to PostgreSQL-ROLLUP()

While migrating my application from DB2 to PostgreSQL. I want to migrate ROLLUP() function in PostgreSQL. Example: SELECT WEEK(SALES_DATE) AS WEEK, DAYOFWEEK(SALES_DATE) AS DAY_WEEK, SUM(SALES) AS UNITS_SOLD FROM SALES GROUP BY ROLLUP ( WEEK(SALES_DATE), DAYOFWEEK(SALES_

[GENERAL] Migration from DB2 to PostgreSQL

While migrating my application from DB2 to PostgreSQL. I want to migrate following functions in PostgreSQL. TO_CHAR() in DB2 which can take three arguments as follows: SELECT TO_CHAR(CURRENT_DATE,'-MM-DD',112.50) FROM SYSIBM.SYSDUMMY1 I am not sure what is the purpose of third argument in T

Re: [GENERAL] Migration from DB2 to PostgreSQL

Am 19.06.2013 08:05, schrieb sachin kotwal: While migrating my application from DB2 to PostgreSQL. I want to migrate following functions in PostgreSQL. Functions in DB2: BLOB()/CLOB() Criteria: Size of character string targeted for cast is more than 1GB. Character String as argument to this f

[GENERAL] Migration from DB2 to PostgreSQL

While migrating my application from DB2 to PostgreSQL. I want to migrate following functions in PostgreSQL. Functions in DB2: BLOB()/CLOB() Criteria: Size of character string targeted for cast is more than 1GB. Character String as argument to this function. How can I migrate this function in

[GENERAL] Migration from DB2 to PostgreSQL

Function in DB2: BLOB()Criteria:Size of character string targeted for cast is more than 1GBHow can I migrate this function into PostgreSQL with above mention criteria. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Migration-from-DB2-to-PostgreSQL-tp5759607.html Sent f

Re: [GENERAL] migration from PointBase to PostgreSQL

On 8/10/2010 12:35 AM, Frank Zhao wrote: We are supposed to migrate PointBase to PostgreSQL. Do you have any advice on how we should approach this, and how to do estimation on the workload? The current PointBase is running on Hub and Spoke by using UniSync for backup and restore purposes. Is th

Re: [GENERAL] migration from PointBase to PostgreSQL

1. get an ascii dump of the source database. 2. check if for consistency if you're ambitious or suspicion by nature (or you've been through this a number of times before and discovered that this is _always_ necessary) 3. create the target database/schema 4. convert source data to target as per

[GENERAL] migration from PointBase to PostgreSQL

We are supposed to migrate PointBase to PostgreSQL. Do you have any advice on how we should approach this, and how to do estimation on the workload? The current PointBase is running on Hub and Spoke by using UniSync for backup and restore purposes. Is there any similar technology of UniSync in

Re: [GENERAL] Migration - not null default '0' -> not null default 0 - confused

On 31/03/2010 15:09, Tom Lane wrote: > Mary's the one who's trying to port forward from some neolithic PG > version. Lots of pain, but hopefully lots of gain too! :-) Ray. -- Raymond O'Donnell :: Galway :: Ireland r...@iol.ie -- Sent via pgsql-general mailing list (pgsql-general@postgresql.o

Re: [GENERAL] Migration - not null default '0' -> not null default 0 - confused

Steve Atkins writes: > On Mar 30, 2010, at 4:23 PM, Wang, Mary Y wrote: >> Now, the source code doesn't work any more. Here is the SQL - INSERT INTO >> activity_log (day,hour,group_id,browser,ver,platform,time,page,type,user_id) >> VALUES >> (20100330,'16','','MOZILLA','5.0','Win','1269990036',

Re: [GENERAL] Migration - not null default '0' -> not null default 0 - confused

On Tuesday 30 March 2010 4:59:30 pm Jeff Davis wrote: > On Tue, 2010-03-30 at 16:32 -0700, Adrian Klaver wrote: > > 8.3 tightened up type casting. You cannot INSERT a '0' without casting it > > to an integer i.e '0'::integer. > > I don't think that's accurate: > > postgres=# select version(); > >

Re: [GENERAL] Migration - not null default '0' -> not null default 0 - confused

On Mar 30, 2010, at 4:23 PM, Wang, Mary Y wrote: > Hi, > > I'm confused. I'm in the process of migrating to 8.3.8. I used pg_dump and > pg_restore command for migration. > Here is my problem. > Here is my old table prior migration: > \d activity_log >Table "activity_log" >

Re: [GENERAL] Migration - not null default '0' -> not null default 0 - confused

On Tue, 2010-03-30 at 16:32 -0700, Adrian Klaver wrote: > 8.3 tightened up type casting. You cannot INSERT a '0' without casting it to > an > integer i.e '0'::integer. I don't think that's accurate: postgres=# select version(); version

Re: [GENERAL] Migration - not null default '0' -> not null default 0 - confused

On Tuesday 30 March 2010 4:49:42 pm Wang, Mary Y wrote: > Ok. Thanks. In that case, I'm going to have a lot of type casting issues. > What's the best way to fix all tables? Write a script to alter those > tables? Any suggestions? > > Mary Wang > > This might help: http://petereisentraut.blogspo

Re: [GENERAL] Migration - not null default '0' -> not null default 0 - confused

30, 2010 4:32 PM To: pgsql-general@postgresql.org Cc: Wang, Mary Y Subject: Re: [GENERAL] Migration - not null default '0' -> not null default 0 - confused On Tuesday 30 March 2010 4:23:39 pm Wang, Mary Y wrote: > Hi, > > I'm confused. I'm in the process of

Re: [GENERAL] Migration - not null default '0' -> not null default 0 - confused

On Tuesday 30 March 2010 4:23:39 pm Wang, Mary Y wrote: > Hi, > > I'm confused. I'm in the process of migrating to 8.3.8. I used pg_dump > and pg_restore command for migration. Here is my problem. > Here is my old table prior migration: > \d activity_log > Table "activity_log

[GENERAL] Migration - not null default '0' -> not null default 0 - confused

Hi, I'm confused. I'm in the process of migrating to 8.3.8. I used pg_dump and pg_restore command for migration. Here is my problem. Here is my old table prior migration: \d activity_log Table "activity_log" Attribute | Type | Modifier ---+-

Re: [GENERAL] migration: parameterized statement and cursor

2010/1/11 Aleksey Onopriyenko : > Hello. > > We are trying to migrate from Informix 9.4 to PostgreSQL. As part of > migration we are porting our client application. > > So we need reimplement such functionality: > 1. Declare a cursor using to _parameterized_ SELECT statement. It should be > possibl

Re: [GENERAL] migration: parameterized statement and cursor

On 1/11/2010 8:16 AM, Aleksey Onopriyenko wrote: Hello. We are trying to migrate from Informix 9.4 to PostgreSQL. As part of migration we are porting our client application. So we need reimplement such functionality: 1. Declare a cursor using to _parameterized_ SELECT statement. It should be po

[GENERAL] migration: parameterized statement and cursor

Hello. We are trying to migrate from Informix 9.4 to PostgreSQL. As part of migration we are porting our client application. So we need reimplement such functionality: 1. Declare a cursor using to _parameterized_ SELECT statement. It should be possible to specify cursor's name (and, perhaps, the

Re: [GENERAL] Migration of db

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 > We have 2 databases test and prod. Now they are out of sync ( of > course they will be to some extent ). But there are some functions in some > schemas. we have to sync from prod to test. What I wanted to ask, is there > any tool that you reco

Re: [GENERAL] Migration of db

akp geek wrote on 31.12.2009 21:45: Hi All - We have 2 databases test and prod. Now they are out of sync ( of course they will be to some extent ). But there are some functions in some schemas. we have to sync from prod to test. What I wanted to ask, is there any tool that you recomme

Re: [GENERAL] Migration of db

On Thu, Dec 31, 2009 at 1:45 PM, akp geek wrote: > Hi All - >           We have 2 databases test and prod. Now they are out of sync ( of > course they will be to some extent ). But there are some functions in some > schemas. we have to sync from prod to test. What I wanted to ask, is there > any t

Re: [GENERAL] Migration of db

2009/12/31 akp geek : > Hi All - >           We have 2 databases test and prod. Now they are out of sync ( of > course they will be to some extent ). But there are some functions in some > schemas. we have to sync from prod to test. What I wanted to ask, is there > any tool that you recommend for v

[GENERAL] Migration of db

Hi All - We have 2 databases test and prod. Now they are out of sync ( of course they will be to some extent ). But there are some functions in some schemas. we have to sync from prod to test. What I wanted to ask, is there any tool that you recommend for version control. Because we are

[GENERAL] Migration from Postgres 7.3 to 8.1.1: Getting No results were returned for function calls

Hello Group, I am in the process of migrating Postgres from version 7.3 to 8.1.1 on the Linux 5 server with JDK 1.6 installed and I am using “postgresql-8.3-604.jdbc4.jar”. When I try to call a Postgres function from my Java code I am receiving the following error. org.postgresql.util.PSQLExcepti

Re: [GENERAL] Migration/Upgrade Problems

"Joshua D. Drake" writes: > Your library problems are likely because you just copied the binary? I > assume you didn't actually install postgresql. That's what it looked like to me --- you can't just copy an executable that's been built on a far newer platform. However, you could run pg_dumpall

Re: [GENERAL] Migration/Upgrade Problems

stevefoss wrote: > > I am trying to upgrade my postgresql data from 7.0.3 to 8.3.7 with marginal > success. I tried pg_dumpall and got the tables but lost most of the data. > I also tried pg_dump but keep getting "FATAL 1: Database "whatever" does not > exist in the system catalog" errors. No i

Re: [GENERAL] Migration/Upgrade Problems

On Fri, 17 Apr 2009 09:19:31 -0700 (PDT), stevefoss wrote: > I am trying to upgrade my postgresql data from 7.0.3 to 8.3.7 with marginal > success. I tried pg_dumpall and got the tables but lost most of the data. > I also tried pg_dump but keep getting "FATAL 1: Database "whatever" does > not >

Re: [GENERAL] Migration/Upgrade Problems

On Fri, Apr 17, 2009 at 09:19:31AM -0700, stevefoss wrote: > > I am trying to upgrade my postgresql data from 7.0.3 to 8.3.7 with > marginal success. I tried pg_dumpall and got the tables but lost > most of the data. I also tried pg_dump but keep getting "FATAL 1: > Database "whatever" does not

[GENERAL] Migration/Upgrade Problems

I am trying to upgrade my postgresql data from 7.0.3 to 8.3.7 with marginal success. I tried pg_dumpall and got the tables but lost most of the data. I also tried pg_dump but keep getting "FATAL 1: Database "whatever" does not exist in the system catalog" errors. I also tried using the latest v

[GENERAL] migration issue

Title: WINiPMail Mail Dear PostgresqlHi! How are things going? I'm tae young in KoreaI'm writing to ask you a favor.Now, we are taking a migration testing about Oracle to enterprisedb (I know, It's not Postgresql issue, but I really want to help anyone about this)Then we've got

[GENERAL] Migration Articles.. ???

Dear All, Am going to do migration of database from one version to another., is there any article or any other document explaining the possibilities and other things. Further Explanation: I have a database in postgres X.Y which has around 90 tables, and lot of data in it. In the next version of

Re: [GENERAL] migration problem

Thank you Tom & co. for your most helpful suggestions. If I may, I'll give a quick resume of my "adventure": In trying to debug this upgrade from php4 to php5 and postgresql 7.4 to 8.3 I have learned much. First trying to set up various debuggers like PHPed, Eclipse with phpeclipse, DEBUG and X

Re: [GENERAL] migration problem

On Fri, May 16, 2008 at 7:23 PM, PJ <[EMAIL PROTECTED]> wrote: > I have a couple of LAN servers set up for learning & developing. One is > FreeBSD 4.10 running apache 1.3 with php4 module and postgresql 7.3 ; the > 7.0 is running apache22, php5 and posstgresql 8.3. > Here's the problem: Everything

Re: [GENERAL] migration problem

Craig Ringer <[EMAIL PROTECTED]> writes: > That function hits the database repeatedly. If the problem is in fact > with a database query that it's generating you need to determine which > one. You could step through the function with a PHP debugger or just > insert log/printing statements in the

Re: [GENERAL] migration problem

PJ wrote: ($_SERVER["DOCUMENT_ROOT"].. and all that is well. However, there seems to be a problem with the sql code which was done by another party. There is a function "checkuser" which is invoked upon login from index.php. The instruction is: checkuser(array(0,1,2,3,4,5,6));.. and th

[GENERAL] migration problem

I have a couple of LAN servers set up for learning & developing. One is FreeBSD 4.10 running apache 1.3 with php4 module and postgresql 7.3 ; the 7.0 is running apache22, php5 and posstgresql 8.3. Here's the problem: Everything is fine on the older machine. I transferred one "WebSite" to the n

Re: [GENERAL] migration of 7.4 to 8.1

sathiya psql wrote: Is there any article describing the migration database from postgresql 7.4to 8.1 The basic tips are: 1. Use pg_dump from 8.1 to dump your 7.4 database 2. Read the release notes for the intervening versions to see what might affect your applications. In particular, the UTF

[GENERAL] migration of 7.4 to 8.1

Is there any article describing the migration database from postgresql 7.4to 8.1

Re: [GENERAL] Migration of /data from 32bit to 8.2 64bit

On Thu, Feb 07, 2008 at 11:26:27AM +0100, Jean-Samuel Reynaud wrote: > Hi All, > > I want to migration an existing database from a 32bit server to a 64bit > server. I will use exactly the same postgresql version (8.2.6). > Did I need to dump the data to do this or a single copy of /data will > wor

[GENERAL] Migration of /data from 32bit to 8.2 64bit

Hi All, I want to migration an existing database from a 32bit server to a 64bit server. I will use exactly the same postgresql version (8.2.6). Did I need to dump the data to do this or a single copy of /data will work ? Is any interger lenght impact on /data ? Thanks, --

Re: [GENERAL] Migration questions for upcoming 8.3 release and fts

Chris Travers wrote: Hi all; I know -hackers is the preferred place to discuss beta releases, but I suspect that this is a further-reaching wuestion among the general community than is typical so I am posting it here. I have been looking at the changes expected for 8.3 and have noticed that

Re: [GENERAL] Migration questions for upcoming 8.3 release and fts

On Wednesday 24 October 2007 21:10, Chris Travers wrote: > Hi all; > > I know -hackers is the preferred place to discuss beta releases, but I > suspect that this is a further-reaching wuestion among the general > community than is typical so I am posting it here. > > I have been looking at the chan

[GENERAL] Migration questions for upcoming 8.3 release and fts

Hi all; I know -hackers is the preferred place to discuss beta releases, but I suspect that this is a further-reaching wuestion among the general community than is typical so I am posting it here. I have been looking at the changes expected for 8.3 and have noticed that tsearch2 has been mod

Re: [GENERAL] Migration from PervasiveSQL

Hi. Sorry, very late reaction... - Original Message - From: "Robert Treat" <[EMAIL PROTECTED]> On Friday 21 September 2007 22:43, Merlin Moncure wrote: On 9/21/07, Robert Treat <[EMAIL PROTECTED]> wrote: > On Thursday 20 September 2007 18:38, Merlin Moncure wrote: > > On 9/20/07, C

Re: [GENERAL] Migration from PervasiveSQL

You might take a look at BtSearch at www.nssdd.com. It will allow you to export all the Btrieve files in a DDF to CSV format. Gil ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

Re: [GENERAL] Migration from PervasiveSQL

What about Perl? DBI? Not sure if it supports PervasiveSQL The OP stated he already had ODBC connectors setup. Yes, I already have ODBC setup. I'm basically just writing a little something myself that uses the existing Pervasive and Postgres tools as much as possible. On a s

Re: [GENERAL] Migration from PervasiveSQL

On Sunday 23 September 2007 23:43, Ow Mun Heng wrote: > On Sat, 2007-09-22 at 16:05 -0400, Robert Treat wrote: > > On Friday 21 September 2007 22:43, Merlin Moncure wrote: > > > On 9/21/07, Robert Treat <[EMAIL PROTECTED]> wrote: > > > > On Thursday 20 September 2007 18:38, Merlin Moncure wrote: >

Re: [GENERAL] Migration from PervasiveSQL

On Sat, 2007-09-22 at 16:05 -0400, Robert Treat wrote: > On Friday 21 September 2007 22:43, Merlin Moncure wrote: > > On 9/21/07, Robert Treat <[EMAIL PROTECTED]> wrote: > > > On Thursday 20 September 2007 18:38, Merlin Moncure wrote: > > > > On 9/20/07, Collin <[EMAIL PROTECTED]> wrote: > > > > >

Re: [GENERAL] Migration from PervasiveSQL

On Friday 21 September 2007 22:43, Merlin Moncure wrote: > On 9/21/07, Robert Treat <[EMAIL PROTECTED]> wrote: > > On Thursday 20 September 2007 18:38, Merlin Moncure wrote: > > > On 9/20/07, Collin <[EMAIL PROTECTED]> wrote: > > > > Well, the subject says it pretty well but to elaborate: > > > > >

Re: [GENERAL] Migration from PervasiveSQL

On 9/21/07, Robert Treat <[EMAIL PROTECTED]> wrote: > On Thursday 20 September 2007 18:38, Merlin Moncure wrote: > > On 9/20/07, Collin <[EMAIL PROTECTED]> wrote: > > > Well, the subject says it pretty well but to elaborate: > > > > > > I have a database from our ERP package that uses btrieve (Perv

Re: [GENERAL] Migration from PervasiveSQL

On Thursday 20 September 2007 18:38, Merlin Moncure wrote: > On 9/20/07, Collin <[EMAIL PROTECTED]> wrote: > > Well, the subject says it pretty well but to elaborate: > > > > I have a database from our ERP package that uses btrieve (PervasiveSQL) > > for it's database engine. I'd like to transition

Re: [GENERAL] Migration from PervasiveSQL

On 9/20/07, Collin <[EMAIL PROTECTED]> wrote: > Well, the subject says it pretty well but to elaborate: > > I have a database from our ERP package that uses btrieve (PervasiveSQL) > for it's database engine. I'd like to transition all of the data to > PostgreSQL. I've been having trouble finding a

[GENERAL] Migration from PervasiveSQL

Well, the subject says it pretty well but to elaborate: I have a database from our ERP package that uses btrieve (PervasiveSQL) for it's database engine. I'd like to transition all of the data to PostgreSQL. I've been having trouble finding a suitable program to automatically get all of the da

Re: [GENERAL] Migration

I think I've already proven (see Scott and Bernhard's replies) that their troll alarms work just fine. Please realize that anyone who took time to reply to this was already checking their E-Mail and being unproductive. Had I not posted this message I may have saved someone say -- 30 seconds. -D

Re: [GENERAL] Migration

Sorry, I couldn't resist putting my toll hat on :} On 9/15/06, Bernhard Weisshuhn <[EMAIL PROTECTED]> wrote: On Fri, Sep 15, 2006 at 12:33:37PM -0400, Daniel Corbe <[EMAIL PROTECTED]> wrote: > I heard from a bunch of PHP guys that Postgres is total crap. Can > anyone recommend a guide for

  1   2   >