[BUGS] BUG #8453: uninitialized memory access in pg_receivexlog and other bugs
The following bug has been logged on the website: Bug reference: 8453 Logged by: Andrew Gierth Email address: and...@tao11.riddles.org.uk PostgreSQL version: 9.3.0 Operating system: any Description: The first snprintf in writeTimeLineHistoryFile in receivelog.c accesses uninitialized data in the "path" variable, thus creating the .tmp file in a random place (usually the current dir, leading to unexpected EXDEV errors on the rename). Also, receivexlog is ignoring .partial and .history files when determining which timeline to start streaming from, which means that if there are two timeline changes that are not separated by a WAL segment switch, it will fail to operate due to attempting to start from a too-old timeline (for which xlogs are not available on the server). Found from my analysis of a report from irc. -- 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 #8451: quantile extension: memory corruption?
On 14.9.2013 14:12, Tomas Vondra wrote: > On 13.9.2013 18:07, stephane.wust...@lip6.fr wrote: >> The following bug has been logged on the website: >> >> Bug reference: 8451 >> Logged by: strexxx >> Email address: stephane.wust...@lip6.fr >> PostgreSQL version: 9.1.9 >> Operating system: Linux 3.8.0-27-generic #40-Ubuntu SMP x86_64 >> Description: >> >> A query such as this one >> COPY (SELECT e,quantile(EXTRACT(EPOCH >> FROM(d)),ARRAY[0,0.1,0.2,0.3,0.4,0.5,0.6,0.7,0.8,0.9,1]) AS d FROM (SELECT >> e,max(time)-min(time) AS d FROM bb RIGHT JOIN (SELECT s,e FROM ss RIGHT JOIN >> (SELECT e FROM ee WHERE h ~* 'blah') AS i0 USING(e)) AS i0 USING >> (sessionid) GROUP BY e,ei) AS i1 GROUP BY e) TO 'full_path/d.csv' WITH >> CSV;" > > Hi, > > this seems like a bug in the "quantile" extension, which is developed > and distributed completely separately from PostgreSQL. So pgsql-bugs is > not the right place to report the issue. > > I reported the issue on github and I'll look into that today/tomorrow > >https://github.com/tvondra/quantile/issues/4 > > so far it seems like a trivial bug in handling NULL values. And indeed it was a bug in handling NULL values - the PG_ARGISNULL happened too late. I plan to do few more improvements before pushing new version to pgxn, but you may grab the sources from github directly. Tomas -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #8452: COPY command pgadmin
The following bug has been logged on the website: Bug reference: 8452 Logged by: kachwahed Email address: kachwa...@hotmail.fr PostgreSQL version: 9.3.0 Operating system: Windows 7 Description: Hello, in short, for pgadmin, there is no way to specify explicit NULL value with nothing, and it's recommanded to allow users to modify and copy generated script. Regards. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #8454: Process returned exit 0 message is showing while taking backup
The following bug has been logged on the website: Bug reference: 8454 Logged by: prakash chandra panda Email address: prakash_pa...@yahoo.com PostgreSQL version: 8.4.1 Operating system: Windows XP SP3 Description: We have been using Newgenlib since last 4years. NewGgenLib has been installed in two desktops. One system used as NewGenLib main server and the other one is used as Backup server. Both system having windows XP SP3. Now we are facing serious problem relating to Backup of database. When we are taking backup in the main server at that time it is showing the message like this 'Process returned exit 0'. After taking the data backup from the main server we restore the backup in another desktop where NGL is installed but it is not working. So kindly tell some possible solutions to fix the above issue. I am waiting your reply. Thanking you prakash chandra panda -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
