On Sat, Mar 1, 2008 at 2:13 AM, Heikki Linnakangas
<[EMAIL PROTECTED]> wrote:
>
>
> I used to think it's a big problem, but I believe the full-page-write
> optimization in 8.3 made it much less so. Especially with the smoothed
> checkpoints: as checkpoints have less impact on response times, you
On Fri, Feb 29, 2008 at 8:19 PM, Florian G. Pflug <[EMAIL PROTECTED]> wrote:
> Pavan Deolasee wrote:
> > What I am thinking is if we can read ahead these blocks in the shared
> > buffers and then apply redo changes to them, it can potentially
> > improve things a lot. If there are multiple read
Magnus Hagander wrote:
Hi!
Does anybody have a good pointer for an example of how to construct an
array in a SRF? Or if not such a pointer, hints on which way is best to
do it? (it'll be an array of text strings, one-dimensional)
(This is from C, if that's not obvious)
I'm sure there are o
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Does anybody have a good pointer for an example of how to construct an
> array in a SRF? Or if not such a pointer, hints on which way is best to
> do it? (it'll be an array of text strings, one-dimensional)
If you can build it in one swoop, use const
Tatsuo Ishii wrote:
On Tue, Feb 19, 2008 at 3:36 AM, Tatsuo Ishii <[EMAIL PROTECTED]> wrote:
I hope so. But the first thing I would like to do is, to implement the
right thing (i.e. following the standard).
I don't see any reason that the proposal gets less performance than
existing functi
Bernd Helmle wrote:
> --On Montag, Februar 25, 2008 14:04:18 -0500 Tom Lane <[EMAIL PROTECTED]>
> wrote:
>
> > The other issue is whether to throw error for year zero, rather than
> > silently interpreting it as 1 BC. I can't recall whether that behavior
> > was intentional at the time, but give
Hi!
Does anybody have a good pointer for an example of how to construct an
array in a SRF? Or if not such a pointer, hints on which way is best to
do it? (it'll be an array of text strings, one-dimensional)
(This is from C, if that's not obvious)
//Magnus
--
Sent via pgsql-hackers mailing l
Tom Lane wrote:
> Gregory Stark <[EMAIL PROTECTED]> writes:
> > "Tom Lane" <[EMAIL PROTECTED]> writes:
> >> It might work to change struct varlena's contents to something like
> >>
> >> char vl_len_[4]; /* Do not touch this field directly! */
> >> char vl_dat[1];
>
craigp <[EMAIL PROTECTED]> writes:
> I was perusing the todo list to see some easy items that I might help out on
> (and get up to speed on postgres hacking)... one of them (with %) seems to
> lead to another:
> ...
> But I'm left a bit confused on what, if anything, can or should be done.
> May
Oops: meant pg_type.typname
and
pg_class.relname.
- Original Message
From: craigp <[EMAIL PROTECTED]>
To: pgsql-hackers@postgresql.org
Sent: Sunday, March 2, 2008 2:36:33 AM
Subject: newbie: renaming sequences task
Hi
-
I
was
perusing
the
todo
list
to
see
some
easy
items
Oops: meant pg_type.typname
and
pg_class.relname.
- Original Message
From: craigp <[EMAIL PROTECTED]>
To: pgsql-hackers@postgresql.org
Sent: Sunday, March 2, 2008 2:36:33 AM
Subject: newbie: renaming sequences task
Hi
-
I
was
perusing
the
todo
list
to
see
some
easy
items
Hi -
I was perusing the todo list to see some easy items that I might help out on
(and get up to speed on postgres hacking)... one of them (with %) seems to lead
to another:
o %Have ALTER TABLE RENAME rename SERIAL sequence names
o Have ALTER SEQUENCE RENAME rename the sequence name
12 matches
Mail list logo
