Re: [BUGS] BUG #8514: cache lookup failed for relation 421062806
On Thu, Oct 10, 2013 at 1:24 AM, shahtejas2...@gmail.com wrote: my postgresql running file . but sometime i found cache lookup failed for relation 421062806 error in postgresql log. can anyone tell me significant of this error. A relation has disappeared even if the session hold a sufficient lock on it, ensuring that the relation have to be present. -- Michael -- 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 #8498: pg_trgm is missing from windows edb package
On Fri, Oct 4, 2013 at 11:36 AM, Paragon Corporation l...@pcorp.us wrote: Disregard my bug complaint. Stupid user error. Btw, the next time you find an error with this installer, you should not use this mailing list for this purpose but contact directly EDB as this installer is maintained by them and not by community. Regards, -- Michael -- 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 #8498: pg_trgm is missing from windows edb package
On Sat, Oct 5, 2013 at 9:38 PM, Dave Page dp...@pgadmin.org wrote: On 5 Oct 2013, at 13:21, Michael Paquier michael.paqu...@gmail.com wrote: On Fri, Oct 4, 2013 at 11:36 AM, Paragon Corporation l...@pcorp.us wrote: Disregard my bug complaint. Stupid user error. Btw, the next time you find an error with this installer, you should not use this mailing list for this purpose but contact directly EDB as this installer is maintained by them and not by community. EDB (and many of it's staff) are part of the community, just as various other companies and their staff who contribute in other ways are. Further, the PostgreSQL installers are offered as 'official' releases on the community website, so it is quite reasonable for users to report bugs here. OK, sorry for my misunderstanding. -- Michael -- 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] Cant start PostgreSQL Using command prompt
On Tue, Sep 17, 2013 at 1:52 AM, Saravanan Nagarajan n.saravana...@gmail.com wrote: In pglog_txt, LOG: could not bind IPv6 socket: No error HINT: Is another postmaster already running on port 33307? If not, wait a few seconds and retry. LOG: could not bind IPv4 socket: No error HINT: Is another postmaster already running on port 33307? If not, wait a few seconds and retry. WARNING: could not create listen socket for localhost FATAL: could not create any TCP/IP sockets But already, i set ipv64 in pg_hba.conf file. My PostgreSQL Version : 9.2.1 This might be caused by something that changed on your Windows environment like the addition of a new software (Anti-virus)? Also, are you sure that your server is not running? Is there any process Postgres.exe listed if you run a simple command tasklist? -- Michael -- 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] Postgis extension bug w/ OpenBSD
On Tue, Sep 17, 2013 at 4:48 PM, Marcelo Bacha dro...@gmail.com wrote: I have an OpenBSD 5.3 server, with PostgreSQL 9.3.0, which seems to work fine. I´m trying to install on it, which always worked fine. Postgres is working fine as you mention, and only PostGIS development failed. Based on the information above which looks to be a library linking problem for your PostGIS installation, this problem is not related to PG. When I try to install the extension for Postgis 2.1.0, I get this error on psql: postgres=# CREATE EXTENSION postgis; ERROR: could not load library /usr/local/pgsql/lib/rtpostgis-2.2.so: dlopen (/usr/local/pgsql/lib/rtpostgis-2.2.so) failed: Cannot load specified object You mention that you are trying to install postgis 2.1, but rtpostgis-2.2.so is part of the PostGIS 2.2 bundle (version currently in development). So which one are you trying to install? The paths seems all to be OK: # ls -l /usr/local/pgsql/lib/*post* -rwxr-xr-x 1 root wheel 1276039 Jul 1 16:50 /usr/local/pgsql/lib/postgis-2.2.so -rwxr-xr-x 1 root wheel 1208861 Jul 1 16:50 /usr/local/pgsql/lib/rtpostgis-2.2.so When I try to preload the rtpostgis shared object setting the LD_PRELOAD environment variable, I get this info on psql: $ psql (...) psql:/usr/local/pgsql/lib/rtpostgis-2.2.so: undefined symbol 'CurrentMemoryContext' psql:/usr/local/pgsql/lib/rtpostgis-2.2.so: undefined symbol 'SPI_tuptable' psql:/usr/local/pgsql/lib/rtpostgis-2.2.so: undefined symbol 'SPI_result' psql:/usr/local/pgsql/lib/rtpostgis-2.2.so: undefined symbol 'InterruptPending' psql:/usr/local/pgsql/lib/rtpostgis-2.2.so: undefined symbol 'SPI_processed' psql (9.2.4) (...) In fact, I´ve been trying to solve this since a long time ago, and with many previous versions of both Postgresql and Postgis, but I´m really stuck Also, what is the output of this command? = ldd /usr/local/pgsql/lib/rtpostgis-2.2.so Are you sure that rtpostgis is linked to the necessary PG libs? -- Michael -- 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 #8452: COPY command pgadmin
On Sat, Sep 14, 2013 at 4:15 PM, kachwa...@hotmail.fr wrote: in short, for pgadmin... This feature request is related to PGAdmin and not Postgres core. You should send such requests to the PGAdmin mailing lists which are listed here: http://www.pgadmin.org/support/list.php Regards, -- Michael -- 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 #8449: ODBC Failure with Access 10
On Thu, Sep 12, 2013 at 10:21 AM, pulsack.he...@gmx.de wrote: Bug reference: 8449 I'm not able to link in Access to the table map. I get an ODBC error and in the table fields are no data, it returns #Name?. Any idea what is wrong ? You should be more precise here: - What is the version of ODBC driver used? - Could you provide a more complete test case or some code that can reproduce this error? Configuration used perhaps? It is going to be difficult to guess what are your problems with such a vague description. Also, this is a problem related to ODBC. So you should send such reports to pgsql-o...@postgresql.org and not this mailing list. Regards, -- Michael -- 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] Cant start PostgreSQL Using command prompt
On Wed, Sep 11, 2013 at 4:00 AM, Saravanan Nagarajan n.saravana...@gmail.com wrote: Hi, I am using PostgreSQL. If am starting the db with System Account/ any domain account using wrapper, the DB is starting fine. If i am trying to start the PostgreSQL DB using command prompt, [Normal mode or Run as administrator.], It wont start. I provided full permission for everyone in Postgres DB Folder. I didn't find any error in pg_log file. I installed DB in 2008 R2 windows machine. My command : pg_ctl -D ..\data -o -p3306 --log D:\logs\pglog.txt start What is exactly the version of Postgres you are trying to use? What is the output of D:\logs\pglog.txt? -- Michael -- 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] Error by restore a database
On Mon, Sep 9, 2013 at 11:38 PM, Sbis-Partner sbis-part...@mail.ru wrote: Hello! When you restore a database error occurs «Pg_restore: creating TABLE dbschema pg_restore: [archiver (db)] Error from TOC entry 1428; 1259 83487 TABLE dbschema User pg_restore: [archiver (db)] could not execute query: ERROR: role User does not exist Command was: ALTER TABLE public.dbschema OWNER TO User ». User and group information are missing in your dump, this information can be retrieved with pg_dumpall. There are two possibilities in your case: - Use the dump you created previously and complete it with data from pg_dumpall --globals-only containing only user and tablespace information - Use a global dump with pg_dumpall with the user information as well as the database The latter solution is more instinctive IMO, but the former solution will work fine as well. -- Michael -- 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 #8440: sevices not started automatically
On Mon, Sep 9, 2013 at 12:55 AM, sabat.jitendr...@gmail.com wrote: The following bug has been logged on the website: Bug reference: 8440 Logged by: Jitendra Sabat Email address: sabat.jitendr...@gmail.com PostgreSQL version: Unsupported/Unknown Operating system: Window server 2012 Description: Currently i am running postgres8.3 but its services is not started automatically when I start the system. I have tried manually start everyday. But sometime it stopped automatically. Note that 8.3 is EOL since February 2013 and is not actually supported by community anymore. So in your case you should consider an upgrade to the latest minor release of 8.3 (you didn't provide which version you are using exactly), or an upgrade to a latest version. It is however hard to have an idea of what is causing your server to stop if you do not provide more information like the startup logs. -- Michael -- 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 #8408: Not exactly correct error messages for failed check in presence of dropped columns.
On Fri, Aug 30, 2013 at 2:13 PM, maxim.bo...@gmail.com wrote:
However, I think error message should filter dropped column and strange null
values (because if a table has a lot dropped column this error message
quickly become completely unreadable).
Yes, this is not really user-friendly. This comes from
ExecBuildSlotValueDescription@execMain.c when generating a string
representation of a tuple. Attached is a patch to make this function
aware of dropped columns when generating the string (usable down to
9.2). However, after some debugging I am seeing that the dropped
column is not seen inside TupleDesc (only the column name is correct)
when calling this function in executor.
Breakpoint 1, ExecBuildSlotValueDescription (slot=0x7fc26412b8e0,
maxfieldlen=64) at execMain.c:1636
1636TupleDesctupdesc = slot-tts_tupleDescriptor;
(gdb) p *tupdesc-attrs[0]
$1 = {
attrelid = 0,
attname = {
data = id, '\0' repeats 61 times
},
atttypid = 23,
attstattarget = -1,
attlen = 4,
attnum = 1,
attndims = 0,
attcacheoff = 0,
atttypmod = -1,
attbyval = 1 '\001',
attstorage = 112 'p',
attalign = 105 'i',
attnotnull = 0 '\0',
atthasdef = 0 '\0',
attisdropped = 0 '\0',
attislocal = 1 '\001',
attinhcount = 0,
attcollation = 0
}
(gdb) p *tupdesc-attrs[1]
$2 = {
attrelid = 0,
attname = {
data = pg.dropped.2, '\0' repeats 35 times
},
atttypid = 23,
attstattarget = -1,
attlen = 4,
attnum = 2,
attndims = 0,
attcacheoff = -1,
atttypmod = -1,
attbyval = 1 '\001',
attstorage = 112 'p',
attalign = 105 'i',
attnotnull = 0 '\0',
atthasdef = 0 '\0',
attisdropped = 0 '\0',
attislocal = 1 '\001',
attinhcount = 0,
attcollation = 0
}
attisdropped is not set to true, only attname is updated to its new value.
When removing an attribute in RemoveAttributeById, it is written in
comment that updating a pg_attribute row triggers a relcache flush for
target relation, but obviously it is not happening. I am missing
something perhaps?
--
Michael
20130901_dropped_column_gen.patch
Description: Binary data
--
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 #8381: data base inconsistancy
On Wed, Aug 14, 2013 at 11:00 PM, David Fetter da...@fetter.org wrote: On Sun, Aug 11, 2013 at 08:06:55AM +, rohit.gupta...@gmail.com wrote: The following bug has been logged on the website: Bug reference: 8381 Logged by: Rohit Gupta Email address: rohit.gupta...@gmail.com PostgreSQL version: Unsupported/Unknown Operating system: linux Description: Background:- There were a large no. of INSERT/UPDATE/DELETE operation being performed on DB. The DB is reindex/vacuum every hour. During reindex/vacuum time one of the DB table value was successfully updated. But later the read query after ~30 seconds read previous values. Is this possible that the update query commit is delayed ? Are there are some known issues of commit during reindex/vacuum. Currently we are using DB version 8.1 Later when we check the DB status (after some days)it was having the correct updated values. We are using default isolation level (Read Committed) PostgreSQL 8.1 has been unsupported since 2010. Once you've upgraded to a supported version, if the problem persists, we may be able to help. You didn't specify the minor version of 8.1 you are using as well. You might as well try to update to the latest version of 8.1, which is 8.1.23, released before it became EOL. However in your case you should definitely upgrade to a newer version... -- Michael -- 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] Recovery.conf PITR by recovery_target_time
It looks that you are missing something. Similarly to what you did, here is an example of PITR using a base backup: 1) Here is my master node doing some archiving: $ psql -c 'show archive_command' -p 5432 archive_command cp -i %p /home/mpaquier/bin/pgsql/archive/node_5432/%f (1 row) 2) Creating data folder of new node using a base backup: pg_basebackup -D ~/bin/pgsql/slave -p 5432 echo port = 5433 ~/bin/pgsql/slave/postgresql.conf This node will run with port 5433. 3) Creating some data: $ psql -c 'CREATE TABLE aa AS SELECT generate_series(1,100) AS a' -p 5432 SELECT 100 $ date 2013-08-12 19:47:33 GMT $ psql -c 'CREATE TABLE bb AS SELECT generate_series(1,100) AS a' -p 5432 SELECT 100 Similarly to what you did, after doing the recovery table bb will not exist on the node recovered with PITR. 4) Preparing recovery for slave: echo restore_command = 'cp -i /home/mpaquier/bin/pgsql/archive/node_5432/%f %p' ~/bin/pgsql/slave/recovery.conf echo recovery_target_time = '2013-08-12 19:47:33 GMT' ~/bin/pgsql/slave/recovery.conf 5) Time to perform the PITR: $ tail -n3 ~/bin/pgsql/slave/pg_log/postgresql-2013-08-12_195441.log LOG: recovery stopping before commit of transaction 1305, time 2013-08-12 19:48:22.436774+00 LOG: recovery has paused HINT: Execute pg_xlog_replay_resume() to continue. Note that in this case the recovery has stopped such as you can check the status of the node before resuming its activity (you can as well enforce the resume if you wish) 6) Now let's check that the node is in a correct state: $ psql -p 5433 psql (9.3beta2) Type help for help. mpaquier=# \d List of relations Schema | Name | Type | Owner +--+---+-- public | aa | table | mpaquier (1 row) And only table aa exists. Here is more input after resume xlog replay. mpaquier=# create table bb (a int); -- Node is still in read-only mode ERROR: 25006: cannot execute CREATE TABLE in a read-only transaction LOCATION: PreventCommandIfReadOnly, utility.c:270 mpaquier=# select pg_xlog_replay_resume(); pg_xlog_replay_resume --- (1 row) mpaquier=# create table bb (a int); CREATE TABLE Et voila! On Mon, Aug 12, 2013 at 7:34 PM, ascot.m...@gmail.com ascot.m...@gmail.com wrote: - check tables from psql: postgres=# select count(1) from test26; count - 260 (1 row) Perhaps you are connecting to the master node and not the node that has been recovered when querying that? Regards, -- Michael
Re: [BUGS] Enable WAL Archive in Replication server
On Mon, Aug 12, 2013 at 1:53 AM, ascot.m...@gmail.com ascot.m...@gmail.com wrote: I want to enable WAL archive on the replica, I am advised that WAL archive can only be enabled on the Master, can you please advise if this is a bug and any workaround available? Archiving a WAL file is only done once its generation has been completed by a master server. A standby node only replays WAL files, copying them from the indicated archive folder with restore_command to its local pg_xlog folder when necessary, and performs no archive actions. http://www.postgresql.org/docs/devel/static/continuous-archiving.html#BACKUP-ARCHIVING-WAL -- Michael -- 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 #8345: PostGre SQL database is crashing
On Wed, Jul 31, 2013 at 2:12 AM, Pavel Stehule pavel.steh...@gmail.comwrote: Hello 2013/7/30 arun...@gmail.com: The following bug has been logged on the website: Bug reference: 8345 Logged by: Arun Kumar Email address: arun...@gmail.com PostgreSQL version: Unsupported/Unknown Operating system: Linux kernel 2.6.29 Description: Currently we have ported PostGRE SQL database on to the Linux kernel 2.6.29 with Motorolla coldfire cross platform. Version of PostgreSQL = 7.4.3. This version is very old, and there are exists lot of upgrade of 7.4.3, so please upgrade to last 7.4 version http://www.postgresql.org/ftp/source/v7.4.30/ is probably last. Yeah, also 7.4 is EOL for 4~5 years, so it is not anymore supported by the community. By the way, a crash could have been caused for many reasons, including failures at the filesystem level, or hardware level. So if you first do not provide more information about the circumstances of the crash, it will be difficult to make a diagnostic of your problems. As Pavel said, also please consider upgrading. -- Michael
Re: [BUGS] BUG #8346: Postgres BDR: Segmentation Fault observed during replication of binary object.
On Wed, Jul 31, 2013 at 6:58 AM, devadas_mal...@yahoo.co.in wrote: The following bug has been logged on the website: Bug reference: 8346 Logged by: Devadas Mallya Email address: devadas_mal...@yahoo.co.in PostgreSQL version: 9.2.0 Operating system: Ubuntu 12.04 Server Edition (64-bit) Description: Hi, I have setup 2 postgres instances for bi-directional replication. I have used the build from here: git clone -b bdr git://git.postgresql.org/git/users/andresfreund/postgres.git Logical replication is not part of the Postgres core yet. As it is currently being developed and in review process, you should not use this mailing list for such reports. So please contact directly the developer in charge of this feature, Andres. I am sure he will be pleased to get bug reports for his work. -- Michael
Re: [BUGS] BUG #8336: pgAgent is not working
On Fri, Jul 26, 2013 at 7:28 PM, harshmailbo...@gmail.com wrote: The following bug has been logged on the website: Bug reference: 8336 Logged by: Harsh Vardhan Upadhyay Email address: harshmailbo...@gmail.com PostgreSQL version: 9.2.2 Operating system: windows Description: Dear Sir/Mam, I have migrated my database from SQL Server to PosgreSQL. All functionality is working fine, but pgAgent is not working. Jobs are creating, but not running. As i have downladed and installed pgAgent, but can't able to regsister its service(postgreSQL Scheduling agent-pgagent ) in services Section. As this is not directly related to Postgres itself but to pgagent, you should directly send your question to its dedicated mailing list: http://www.pgadmin.org/support/list.php -- Michael
Re: [BUGS] BUG #8324: Missing script
On Tue, Jul 23, 2013 at 2:02 PM, floripa...@gmail.com wrote: The following bug has been logged on the website: Bug reference: 8324 Logged by: Robert Stone Email address: floripa...@gmail.com PostgreSQL version: 9.2.4 Operating system: Debian 3.9-1-amd64 #1 SMP Debian 3.9.8-1 x86_64 GN Description: Downloaded the 9.2.4 source and compiled it. There is NO pg_upgrade script in the 9.2/bin directory. I thought that I have to run this script to upgrade my database from 9.1 to 9.2. Can I run the 9.1 version of pg_upgrade? Please advise. pg_upgrade is a contrib module, so you will find it in contrib/pg_upgrade. Note that when performing an upgrade you will also need to install the extension called pg_upgrade_support in the server to-be-upgraded. It is located in contrib/pg_upgrade_support. -- Michael
Re: [BUGS] BUG #8325: Missing script II
On Tue, Jul 23, 2013 at 2:24 PM, floripa...@gmail.com wrote: The following bug has been logged on the website: Bug reference: 8325 Logged by: Robert Stone Email address: floripa...@gmail.com PostgreSQL version: 9.2.4 Operating system: Linux roblaptop 3.9-1-amd64 #1 SMP Debian 3.9.8-1 Description: Since my previous report discovered pg_upgrade sitting in a directory named contrib. Tried to compile it but the following errors occurred:- root@roblaptop:/home/postgres/v9.2/postgresql-9.2.4/contrib/pg_upgrade# make gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -DFRONTEND -DDLSUFFIX=\.so\ -I. -I../../src/interfaces/libpq -I. -I. -I../../src/include -D_GNU_SOURCE -c -o check.o check.c In file included from ../../src/include/postgres.h:48:0, from check.c:10: ../../src/include/utils/elog.h:69:28: fatal error: utils/errcodes.h: No such file or directory compilation terminated. make: *** [check.o] Error 1 root@roblaptop:/home/postgres/v9.2/postgresql-9.2.4/contrib/pg_upgrade# You should compile first the main code tree in src/. This will help ;) -- Michael
Re: [BUGS] BUG #8286: severe bug in auth
On Fri, Jul 5, 2013 at 8:11 AM, e...@inter.net wrote: The following bug has been logged on the website: Bug reference: 8286 Logged by: Eike Dierks Email address: e...@inter.net PostgreSQL version: 9.2.4 Operating system: CentOS release 6.4 Description: I believe to have found a severe bug in auth. I don't want to post that here. If you need to report a security problem, please use the steps described here to take proper actions: http://www.postgresql.org/support/security/ -- Michael -- 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 #8255: encoding latin1
On Wed, Jun 26, 2013 at 9:21 PM, gabriel...@santamonicace.com.br wrote: The following bug has been logged on the website: Bug reference: 8255 Logged by: gabriel Email address: gabriel...@santamonicace.com.br PostgreSQL version: 8.4.4 You are missing many minor releases. The latest version of 8.4 is 8.4.17. It will also fall in EOL last year, so think about an upgrade! Operating system: windows xp Description: Good afternoon, I live in Brazil and I need to create a database with encoding LATIN1. how can I make this database. I use windows xp and postgreSQL. please send a tutorial on how to makeThank you. initdb has an option called --encoding allowing to override the encoding of the template database when initializing server. You can also specify an encoding with CREATE DATABASE, but use template0 as template database in this case. postgres=# create database foo encoding 'LATIN1' TEMPLATE template0; CREATE DATABASE For reference: http://www.postgresql.org/docs/8.4/static/app-initdb.html http://www.postgresql.org/docs/9.3/static/sql-createdatabase.html -- Michael -- 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 #8193: A few cosmetic misspell fixes.
On Fri, May 31, 2013 at 1:51 AM, vla...@gmail.com wrote: The following bug has been logged on the website: Bug reference: 8193 Logged by: Lajos Veres Email address: vla...@gmail.com PostgreSQL version: 9.2.4 Operating system: Linux Description: Found a few small misspell with this: https://github.com/vlajos/misspell_fixer I created a small patch here: http://www.pastebin.ca/2385261 Referring a patch with an external link is bad practice as the external service you use could disappear, making this patch lost at the same time. Please attach patches directly with the mails you send. For the patch, yes OK there are some spell mistakes. However this patch should only apply on master branch, and not 9.2 as referenced above. Also, changing the structure name to Extension does not look to be appropriate as it is a generic name... -- Michael
Re: [BUGS] BUG #8197: Error Message When trying to install PS8.1
On Sat, Jun 1, 2013 at 3:34 AM, healthycomput...@persona.ca wrote: initdb: removing contents of data directory C:/Program Files (x86)/PostgreSQL/8.1/data Only Postgres 8.1 is not supported anymore by the community for a couple of years. You should use a newer version. -- Michael
Re: [BUGS] BUG #7983: Problem with pgAgent.
On Fri, Mar 22, 2013 at 5:12 AM, marcelo_math...@oi.com.br wrote: run a batch in pgAgent the following error occurs. DEBUG: Checking for jobs to run DEBUG: Sleeping... sh: /tmp/pga_GvQxqM/5_9.scr: Permission denied DEBUG: Clearing inactive connections DEBUG: Connection stats: total - 1, free - 0, deleted - 0 DEBUG: Checking for jobs to run DEBUG: Sleeping... I have no idea what may be happening. The / tmp is allowed for everyone. Isn't this bug something related with pgAdmin? You should perhaps report this bug to their dedicated ML instead: http://www.pgadmin.org/support/list.php -- Michael
Re: [BUGS] Nested xmlagg doesn't give a result 9.2.3
On Tue, Feb 19, 2013 at 5:50 PM, Peter Kroon plakr...@gmail.com wrote: Also no result with FROM __my_table LIMIT 1; I'm having correct results with PG 9.2 by using either xmlagg or xmlelement. For example: postgres=# SELECT xmlelement(name el_name, id) FROM __table LIMIT 1; xmlelement -- el_name1/el_name Or: postgres=# SELECT xmlagg(xmlelement(name el_name, id)) FROM __table; xmlagg -- el_name1/el_nameel_name2/el_name (1 row) Btw, such simple tests would have failed on the buildfarm for regression xml.sql, so this looks to be an error in your environment. Don't you have for example problems with the client application you use? -- Michael
Re: [BUGS] Nested xmlagg doesn't give a result 9.2.3
Hi, With your query and such tables: create table __table (id int); insert into __table values (1),(2); create table __table_to_table (id int, table_id int); insert into __table_to_table values (1, 1),(2, 2); I am getting consistent results with 9.2.1 and 9.2.3 on my Linux box, hence: xmlelement --- s_as_b i=1s_c i=1//s_bs_b i=2s_c i=2//s_b/s_a (1 row) Could you be more explicit about the result you expect and the output differences you see between those versions? Regards, -- Michael
