Daniel Farina writes:
> Thinking unnecessary. Motion is progress. Here is a patch that uses
> this exact plan: pgport for the tables, broken out into a header file
> that is included in the building of libpgport. I have confirmed by
> objdump -t that multiple copies of the table are not include
On Thu, Feb 16, 2012 at 6:09 AM, Robert Haas wrote:
> On Fri, Feb 3, 2012 at 7:33 PM, Daniel Farina wrote:
>> Ah, yes, I think my optimizations were off when building, or
>> something. I didn't get such verbosity at first, and then I remember
>> doing something slightly different and then gettin
On Fri, Feb 3, 2012 at 7:33 PM, Daniel Farina wrote:
> Ah, yes, I think my optimizations were off when building, or
> something. I didn't get such verbosity at first, and then I remember
> doing something slightly different and then getting a lot of output.
> I didn't pay attention to the build s
On Tue, Jan 31, 2012 at 3:43 PM, Tom Lane wrote:
> Daniel Farina writes:
>> On Tue, Jan 17, 2012 at 2:14 AM, Daniel Farina wrote:
>>> See the attached patch. It has a detailed cover letter/comment at the
>>> top of the file.
>
>> I have amended that description to be more accurate.
>
> I looked
Daniel Farina writes:
> On Tue, Jan 17, 2012 at 2:14 AM, Daniel Farina wrote:
>> See the attached patch. It has a detailed cover letter/comment at the
>> top of the file.
> I have amended that description to be more accurate.
I looked at this a bit, and it seems to go considerably further than
At 2012-01-17 13:43:11 -0800, dan...@heroku.com wrote:
>
> > See the attached patch. It has a detailed cover letter/comment at
> > the top of the file.
The patch looks good, but the resetxlog and controldata Makefile hunks
didn't apply. I don't know why, but I've attached updated versions of
thos
Daniel Farina writes:
> Copying CRC32 implementations everywhere is not the worst thing, but I
> find it inadequately explained why it's necessary for now, at least.
Agreed, but I don't care for your proposed solution (put it in
libpgport) because that assumes a fact not in evidence, namely that
On Mon, Jan 16, 2012 at 6:18 PM, Robert Haas wrote:
> I think you make a compelling case.
That's enough for me to just do it. Expect a patch soon.
--
fdr
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailp
On Mon, Jan 16, 2012 at 8:09 PM, Daniel Farina wrote:
> On Mon, Jan 16, 2012 at 4:56 PM, Daniel Farina wrote:
>> I have been working with xlogdump and noticed that unfortunately it
>> cannot be installed without access to a postgres build directory,
>> which makes the exported functionality in sr
On Mon, Jan 16, 2012 at 4:56 PM, Daniel Farina wrote:
> I have been working with xlogdump and noticed that unfortunately it
> cannot be installed without access to a postgres build directory,
> which makes the exported functionality in src/include/utils/pg_crc.h
> useless unless one has access to
I have been working with xlogdump and noticed that unfortunately it
cannot be installed without access to a postgres build directory,
which makes the exported functionality in src/include/utils/pg_crc.h
useless unless one has access to pg_crc.o -- which would only happen
if a build directory is lyi
11 matches
Mail list logo
