Re: [BUGS]
i used this link http://www.enterprisedb.com/products-services-training/pgdownload#windows On Sun, Mar 24, 2013 at 9:13 AM, Hana'a AL-Theiabat wrote: > this application use PostgreSQL 8.0.0-rc1 on windows xp ,, it is for > wireless sensors nodes, > however from this link i try to download PostgreSQL 8.3 but it is require > password during instillation ?? have you any idea ? > > > On Sun, Mar 24, 2013 at 3:26 AM, John R Pierce wrote: > >> On 3/23/2013 7:22 AM, News Subsystem wrote: >> >>> the version of pgsql is PostgreSQL 8.0.0-rc1 >>> >>> anyone have any idea to solve this ? >>> >> >> step 1, install a supported version. 8.0 has been EOSL for several >> years now, the first robust version of PostgreSQL on MS Windows is 8.3, adn >> even that is EOL now, 8.4.16 is the oldest version currently supported. >> 8.0.0-Rc1 was a beta release of the first release of the 8.0 series, which >> got up to like 8.0.26 before it was discontinued. 8.0.0 was released in >> January 2005, its 2013 now. >> >> I have no idea what Moteview 2.0 is, never heard of it. This package >> supports PostgreSQL ? what version(s) do they recommend? does it require >> additional database connectivity components like ODBC, or NPGSQL or ? >> >> anyways, I don't believe this is a postgresql bug, so doesn't belong on >> this list. >> >> >> -- >> john r pierce 37N 122W >> somewhere on the middle of the left coast >> >> >
[BUGS] BUG #7997: View the data in stretch column spacing, stop working
The following bug has been logged on the website: Bug reference: 7997 Logged by: penkee Email address: pen...@163.com PostgreSQL version: 9.2.3 Operating system: window7 Description: In edit data window,the name of someone column is too long.So I stretch this column,but 'PostgreSQL Tools stop working ' out. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7940: Auto increment issue
Hi Josh, Thanks for your reply .We are backing up in a file and restoring it into DB .We have a product which supports multiple databases where data migration between two different databases say POSTGRES and MySQL can be done. setval might be the solution for my problem but it will be better if u find max value and auto increment without using specific methods for this problem. Thanks, Krishna On Mon, Mar 18, 2013 at 11:09 AM, krishnakumar wrote: > Hi Josh, > > Thanks for your reply .We are backing up in a file and restoring > it into DB .We have a product which supports multiple databases where data > migration between two different databases say POSTGRES and MySQL can be > done. setval might be the solution for my problem but it will be better if > u find max value and auto increment without using specific methods for this > problem. > > Thanks, > Krishna > > On Mon, Mar 18, 2013 at 10:37 AM, krishnakumar < > krishnakumar.e...@gmail.com> wrote: > >> >> >> -- Forwarded message -- >> From: Josh Kupershmidt >> Date: Thu, Mar 14, 2013 at 8:43 PM >> Subject: Re: [BUGS] BUG #7940: Auto increment issue >> To: krishnakumar.e...@gmail.com >> Cc: pgsql-bugs@postgresql.org >> >> >> On Wed, Mar 13, 2013 at 4:01 AM, wrote: >> >> > Hi, >> > I'm using PostgreSQL 9.0.1 and driver PostgreSQL 9.0 JDBC4 and my >> OS >> > is Ubuntu.I'm using serial type for auto-incrementing column id in my >> table >> > everything works fine .when i stop my application and restart the >> > application its fine but when i backup DB and then restore it back >> manually >> > i'm inserting id column by myself during restoring...after restore If i >> > start the application, the id column doesn't start incrementing from >> maximum >> > value of id instead starts from begining (i.e., 1) and getting >> duplicate key >> > value violates unique constraint "smsserver_out_pkey" Detail: Key >> (id)=(1) >> > already exists till upto restored number of entries. ...what is the >> solution >> > to over come this issue ... >> >> [snip] >> >> > My Insert Query for restoring the database >> > INSERT INTO >> > >> >> smsserver_out(id,type,recipient,text,wap_url,wap_expiry_date,wap_signal,create_date,originator,encoding,status_report,flash_sms,src_port,dst_port,sent_date,ref_no,priority,status,errors,gateway_id) >> >> Well, you didn't specify how exactly you are backing up and restoring >> the table, although from the INSERT snippet you showed it looks like >> you're not using pg_dump. If you were using pg_dump, it would handle >> resetting the sequence behind smsserver_out.id to its value at the >> time of the dump. If you are using some other method to backup and >> reload the table, you will have to include a call to setval() to set a >> sane value for the sequence. For the record, reimplementing pg_dump is >> usually a bad idea. >> >> Josh >> >> >
Re: [BUGS]
this application use PostgreSQL 8.0.0-rc1 on windows xp ,, it is for wireless sensors nodes, however from this link i try to download PostgreSQL 8.3 but it is require password during instillation ?? have you any idea ? On Sun, Mar 24, 2013 at 3:26 AM, John R Pierce wrote: > On 3/23/2013 7:22 AM, News Subsystem wrote: > >> the version of pgsql is PostgreSQL 8.0.0-rc1 >> >> anyone have any idea to solve this ? >> > > step 1, install a supported version. 8.0 has been EOSL for several years > now, the first robust version of PostgreSQL on MS Windows is 8.3, adn even > that is EOL now, 8.4.16 is the oldest version currently supported. > 8.0.0-Rc1 was a beta release of the first release of the 8.0 series, which > got up to like 8.0.26 before it was discontinued. 8.0.0 was released in > January 2005, its 2013 now. > > I have no idea what Moteview 2.0 is, never heard of it. This package > supports PostgreSQL ? what version(s) do they recommend? does it require > additional database connectivity components like ODBC, or NPGSQL or ? > > anyways, I don't believe this is a postgresql bug, so doesn't belong on > this list. > > > -- > john r pierce 37N 122W > somewhere on the middle of the left coast > >
[BUGS] JRV problem with pg_upgrade
Hello, I'am a database administrateur and I get trouble to upgrade database postgres from 8.4.6 to 9.2.3. During pg_upgrade, I can't start the old cluster with parameter -c listen_addresses='' This syntax work to start the old cluster and to access to the database "/distrib/postgresql/app/chfdba/produit/8.4.6/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/distrib/postgresql/data/chorus_formulaires/data" -o "-p 50432 -c autovacuum=off -c autovacuum_freeze_max_age=20 -c listen_addresses='*' -c unix_socket_permissions=0700" start This syntax doesn't work to start the old cluster "/distrib/postgresql/app/chfdba/produit/8.4.6/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/distrib/postgresql/data/chorus_formulaires/data" -o "-p 50432 -c autovacuum=off -c autovacuum_freeze_max_age=20 -c listen_addresses='' -c unix_socket_permissions=0700" start But pg_upgrade use this "bad" syntax even I try to force -c listen_addresses='*' pg_upgrade -c -d /distrib/postgresql/data/chorus_formulaires/data -D /distrib/postgresql/data/chorus_formulaires/data/9.2.3 -b /distrib/postgresql/app/chfdba/produit/8.4.6/bin -B /distrib/postgresql/app/chfdba/produit/9.2.3/bin -o "-c listen_addresses='*'" more pg_upgrade_server.log could not connect to old postmaster started with the command: "/distrib/postgresql/app/chfdba/produit/8.4.6/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/distrib/postgresql/data/chorus_formulaires/data" -o "-p 50432 -c autovacuum=off -c autovacuum_freeze_max_age=20 -c listen_addresses='*' -c listen_addresses='' -c unix_socket_permissions=0700" start Failure, exiting I don't know how to workaround this problem ? Best regards, Jacques ravalet
Re: [BUGS]
On 3/23/2013 11:13 PM, Hana'a AL-Theiabat wrote: this application use PostgreSQL 8.0.0-rc1 on windows xp ,, it is for wireless sensors nodes, I think you should contact the application vendor for support if they are using such old and obsolete postgres versions. however from this link i try to download PostgreSQL 8.3 but it is require password during instillation ?? have you any idea ? probably the password to the `postgres` service account created by the 8.0 install. control panel -> admin tools -> computer management -> local users and groups -> users, find the postgres account, and set a new password via right click... then install the newer postgres and tell it what that password is. -- john r pierce 37N 122W somewhere on the middle of the left coast -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7986: base backup copy all files from tablespace, not only needed data
On 23.03.2013 16:39, eshkin...@gmail.com wrote: The following bug has been logged on the website: Bug reference: 7986 Logged by: Sergey Burladyan Email address: eshkin...@gmail.com PostgreSQL version: 9.2.3 Operating system: Debian GNU/Linux 7.0 (wheezy) Description: I have one tablespace dir with multiple versions: $ ls -la ~/inst/var/l/ итого 16 drwx-- 4 seb seb 4096 Мар 23 18:26 . drwxr-xr-x 7 seb seb 4096 Мар 23 18:28 .. drwx-- 3 seb seb 4096 Мар 23 18:24 PG_9.2_201204301 drwx-- 3 seb seb 4096 Мар 23 18:26 PG_9.3_201303201 ../pg-dev-master/bin/pg_basebackup -Ft -D backup copy all subdirectorys from tablespace dir: $ tar -tf backup/16384.tar PG_9.2_201204301/ PG_9.2_201204301/12042/ PG_9.2_201204301/12042/16385 PG_9.3_201303201/ PG_9.3_201303201/12070/ PG_9.3_201303201/12070/16385 PG_9.3_201303201/12070/16390 PG_9.3_201303201/12070/16388 IMHO it must copy only self version dir PG_9.3_201303201 Agreed. Fixed, thanks for the report. - Heikki -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7983: Problem with pgAgent.
Good afternoon, Dave. That was it, bingo! Thank you for your help. -- View this message in context: http://postgresql.1045698.n5.nabble.com/BUG-7983-Problem-with-pgAgent-tp5749215p5749598.html Sent from the PostgreSQL - bugs mailing list archive at Nabble.com. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
