The following bug has been logged on the website:
Bug reference: 8097
Logged by: Wouter Boasson
Email address: wouter.boas...@rivm.nl
PostgreSQL version: 9.1.9
Operating system: Scientific Linux 6.1 32bit
Description:
pg_dump produces incomplete data dumps for large t
The following bug has been logged on the website:
Bug reference: 8098
Logged by: Catherine Devlin
Email address: catherine.dev...@gmail.com
PostgreSQL version: 9.2.4
Operating system: Ubuntu 12.10
Description:
Actually, bug is in 9.3devel from the git repo, but that's
bmoha...@gmail.com writes:
> $ psql seo
> psql (9.0.4)
> Type "help" for help.
> *** glibc detected *** psql: free(): invalid next size (normal):
> 0x1553a9d0 ***
> === Backtrace: =
> /lib64/libc.so.6[0x321b871684]
> /lib64/libc.so.6(cfree+0x8c)[0x321b874ccc]
> /opt/postgres/9.
vaiay...@gmail.com writes:
> 3. compile prepare.c (attached)
I see no such attachment ...
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
catherine.dev...@gmail.com writes:
> root@illyan:/etc/init.d# cat /usr/local/pgsql/data/serverlog
> /usr/local/pgsql/bin/postmaster: invalid option -- 'I'
> Try "postmaster --help" for more information.
Meh. Looks like Peter broke this in commit
87306184580c9c49717b00d48a2f9e717f21e0a8. Thanks
wouter.boas...@rivm.nl writes:
> pg_dump produces incomplete data dumps for large tables in directory mode
> (-Fd).
> The maximum output file size seems to be 2147483647 bytes (2GB), when
> setting --compress=0 the output seems to be complete (uncompressed size 5GB
> and 20GB).
I can't replicate t
Hi all,
Forgot to attach the file prepare.c with steps for the bug.
Here is the file attached.
- Nachiket
#include
#include
#include "libpq-fe.h"
int
main()
{
PGconn *conn;
PGresult *res;
conn = PQconnectdb("host=localhost dbname=postgres");
if (PQstatus(conn) != CONNECTION_OK)
{
exit(
