On Fri, Feb 15, 2013 at 3:49 PM, Heikki Linnakangas
wrote:
>> While this solution would help solve my issue, it assumes that the
>> correct amount of WAL files are actually there. Currently the docs for
>> setting up a standby refer to "24.3.4. Recovering Using a Continuous
>> Archive Backup", and
On 15.2.2013 01:02, Tomas Vondra wrote:
> On 14.2.2013 22:24, Alvaro Herrera wrote:
>> Alvaro Herrera escribió:
>>> Here's a ninth version of this patch. (version 8 went unpublished). I
>>> have simplified a lot of things and improved some comments; I think I
>>> understand much of it now. I thi
Hi,
During logical decoding toast tuples are decoded separately from the
main tuple. Works nicely. To make the main table's HeapTuple actually
easily useable the tuple needs to be "reconstructed" to not point to
disk anymore but to the separately reconstructed tuples.
There are two ways to do thi
On 02/13/2013 11:36 AM, Andrew Dunstan wrote:
Therefore, I would like to propose different names:
Existing Name Proposed Name
--
json_array_length() array_length() or length() or size()
json_each()
On 2013-02-16 17:42:31 +0100, Andres Freund wrote:
> +/* --
> + * toast_datum_differs -
> + *
> + * Determine whether two toasted datums are the same and don't have to be
> + * stored again.
> + * --
> + */
> +static bool
> +toast_datum_differs(struct varlena *old_value, struct va
Robert Haas wrote:
> On Fri, Feb 15, 2013 at 8:01 PM, Kevin Grittner wrote:
>> There is one odd aspect to pg_dump, but I think the way it is
>> behaving is the best way to handle it, although I invite other
>> opinions. If you load from pg_dump output, it will try to
>> populated materialized v
On Sun, Jan 13, 2013 at 07:54:11AM +0100, Pavel Stehule wrote:
> related to
> http://www.postgresql.org/message-id/cafj8prdtavfnrazwet+ewmfrbdzffva8w17kk_e12fb6t-z...@mail.gmail.com
>
> boolean domains is serialised to string different than boolean
>
> postgres=# CREATE DOMAIN booldomain as bool
Bruce Momjian wrote:
> On Fri, Feb 15, 2013 at 08:24:16PM -0500, Robert Haas wrote:
>> On Fri, Feb 15, 2013 at 8:01 PM, Kevin Grittner wrote:
>>> There is one odd aspect to pg_dump, but I think the way it is
>>> behaving is the best way to handle it, although I invite other
>>> opinions. If you
2013/2/16 Noah Misch :
> On Sun, Jan 13, 2013 at 07:54:11AM +0100, Pavel Stehule wrote:
>> related to
>> http://www.postgresql.org/message-id/cafj8prdtavfnrazwet+ewmfrbdzffva8w17kk_e12fb6t-z...@mail.gmail.com
>>
>> boolean domains is serialised to string different than boolean
>>
>> postgres=# CRE
On Sat, Feb 16, 2013 at 09:53:14AM -0800, Kevin Grittner wrote:
> Robert Haas wrote:
> > On Fri, Feb 15, 2013 at 8:01 PM, Kevin Grittner wrote:
> >> There is one odd aspect to pg_dump, but I think the way it is
> >> behaving is the best way to handle it, although I invite other
> >> opinions. If
On Feb 16, 2013, at 8:57 AM, Andrew Dunstan wrote:
> I have had a look at doing something like this with the json_get functions.
> The trouble is that the best way to do it is to have json_get take "variadic
> any", but then string literals come in as unknown rather than as text, which
> makes
On 2013-02-16 11:55:26 -0800, David E. Wheeler wrote:
> On Feb 16, 2013, at 8:57 AM, Andrew Dunstan wrote:
>
> > I have had a look at doing something like this with the json_get functions.
> > The trouble is that the best way to do it is to have json_get take
> > "variadic any", but then string
On 02/16/2013 03:05 PM, Andres Freund wrote:
On 2013-02-16 11:55:26 -0800, David E. Wheeler wrote:
On Feb 16, 2013, at 8:57 AM, Andrew Dunstan wrote:
I have had a look at doing something like this with the json_get functions. The trouble
is that the best way to do it is to have json_get tak
Continuing to look at this patch ... I'm wondering if any particular
discussion went into choosing the FDW option names "nspname", "relname",
and "colname". These don't seem to me like names that we ought to be
exposing at the SQL command level. Why not just "schema", "table",
"column"? Or perha
On Fri, Feb 15, 2013 at 12:12:03PM -0500, Bruce Momjian wrote:
> On Thu, Feb 14, 2013 at 07:21:27PM -0500, Tom Lane wrote:
> > Bruce Momjian writes:
> > > Agreed. The attached patch modifies pg_check_dir() to report about
> > > invisible and lost+found directory entries, and give more helpful
> >
On Feb 16, 2013, at 12:47 PM, Andrew Dunstan wrote:
> To answer David's point, there is no point in having both
>
>get(json,text)
>get(json, variadic text[])
>
> since the second can encompass the first, and having both would make calls
> ambiguous.
Oh. Well then how about
get(jso
On Sun, Feb 17, 2013 at 8:44 AM, Tom Lane wrote:
> Continuing to look at this patch ... I'm wondering if any particular
> discussion went into choosing the FDW option names "nspname", "relname",
> and "colname".
IIRC, there was no deep discussion about those option names. I simply
chose "relname
Tomas Vondra wrote:
> I've been thinking about this (actually I had a really weird dream about
> it this night) and I think it might work like this:
>
> (1) check the timestamp of the global file -> if it's too old, we need
> to send an inquiry or wait a bit longer
>
> (2) if it's new enough
On Tuesday, February 12, 2013 2:49 AM Heikki Linnakangas wrote:
On 04.02.2013 17:32, Alvaro Herrera wrote:
> Phil Sorber wrote:
>> On Mon, Feb 4, 2013 at 10:16 AM, Alvaro Herrera
>> wrote:
>>> Phil Sorber wrote:
On Mon, Feb 4, 2013 at 9:13 AM, Alvaro Herrera
wrote:
>>>
> I think this
19 matches
Mail list logo