pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Invalid memory alloc querying field type bytea
2+ messages / 2 participants
[nested] [flat]

* Invalid memory alloc querying field type bytea
@ 2020-06-17 18:24  Thompson, Shon <Shon.Thompson@MaineGeneral.org>
  0 siblings, 1 reply; 2+ messages in thread

From: Thompson, Shon @ 2020-06-17 18:24 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>

I'm getting errors when I query a table that uses data type bytea.  I can query the table if I don't include the field for data type bytea.  Here are the two error messages I get.  The first error is one generated from visual studio:

"ERROR: XX000: invalid memory alloc request size 1294068297"

This error is what I get when I use pgAdmin:

"ERROR:  invalid memory alloc request size 1881675850
SQL state: XX000"

Please let me know if you need any additional information to determine if this is a bug.  Thanks.

Shon

[MGMCEmailSig]
Shon Thompson
Senior Application Engineer
Information Technology Division
Office:  207-624-4391
Cell:  207-330-9501
Shon.Thompson@MaineGeneral.org<mailto:Shon.Thompson@MaineGeneral.org>

Attachments:

image001.jpg (image/jpeg, 4.4K) download view image
^ permalink raw reply [nested|flat] 2+ messages in thread

* Re: Invalid memory alloc querying field type bytea
@ 2020-06-17 18:45  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Thompson, Shon <Shon.Thompson@MaineGeneral.org>
  0 siblings, 0 replies; 2+ messages in thread

From: Tom Lane @ 2020-06-17 18:45 UTC (permalink / raw)
  To: Thompson, Shon <Shon.Thompson@MaineGeneral.org>; +Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>

"Thompson, Shon" <Shon.Thompson@MaineGeneral.org> writes:
> I'm getting errors when I query a table that uses data type bytea.  I can query the table if I don't include the field for data type bytea.  Here are the two error messages I get.  The first error is one generated from visual studio:
> "ERROR: XX000: invalid memory alloc request size 1294068297"

Looks like a corrupt-data problem.  I doubt it's directly the fault of
bytea; any variable-length field would have given a similar type of error,
because what this seems to be is a damaged field length word.

Do you see any clearly bogus data in other columns of the table?  That
might help isolate which row(s) have gotten damaged.  It seems somewhat
unlikely that only the bytea field header would be clobbered and not
any adjacent data.

The questions you should be asking yourself include whether your PG
version is up-to-date and whether the storage stack is reliable.

			regards, tom lane





^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2020-06-17 18:45 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-06-17 18:24 Invalid memory alloc querying field type bytea Thompson, Shon <Shon.Thompson@MaineGeneral.org>
2020-06-17 18:45 ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox