From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Yessica Brinkmann <yessica(dot)brinkmann(at)gmail(dot)com>, Jony Cohen <jony(dot)cohenjo(at)gmail(dot)com>, laurenz(dot)albe(at)cybertec(dot)at |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: I think that my data is saved correctly, but when printing again, other data appears |
Date: | 2019-10-28 11:03:21 |
Message-ID: | efb6bd16-268c-5360-3206-7f0fb5fef523@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/27/19 8:01 PM, Yessica Brinkmann wrote:
> Thank you so much for the answers.
> By telling me this: "MemoryContextStrdup enables you to create a copy of
> a string in an explicitly specified memory context." I better understood
> the function of MemoryContextStrdup.
> And thank you very much to Mr. Jony Cohen for giving me the reference of
> his work. I really was already researching about his work, and I
> included it in the state of the art of my thesis, but I didn't look at
> the source code.
> I will be looking at the source code for a help, and especially in this
> case to see for the moment, the maintenance of the context for its
> subsequent restoration.
For better understanding of how Postgres manages memory, you might want
to also read this:
https://github.com/postgres/postgres/blob/master/src/backend/utils/mmgr/README
and possibly browse through this:
https://github.com/postgres/postgres/blob/master/src/backend/utils/mmgr/mcxt.c
HTH,
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
From | Date | Subject | |
---|---|---|---|
Next Message | Basques, Bob (CI-StPaul) | 2019-10-28 13:00:07 | Re: SQL pretty pritner? |
Previous Message | Yessica Brinkmann | 2019-10-28 00:01:50 | Re: I think that my data is saved correctly, but when printing again, other data appears |