On Fri, Apr 18, 2014 at 12:00 PM, Peter Eisentraut wrote:
>
> On 4/17/14, 8:24 PM, Tom Lane wrote:
> > We could in fact implement #2, I imagine, by destroying and recreating
> > the entire language interpreter. So I could imagine implementing a
> > "DISCARD INTERPRETERS" kind of command that woul
On Sat, Apr 19, 2014 at 05:50:17PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > On Wed, Feb 26, 2014 at 10:21:03PM -0500, Tom Lane wrote:
> >> Oh, I'd forgotten about that thread. I never particularly liked the patch
> >> as presented: like Robert, I thought it far too complicated. My
> >>
Hi,
Currently, unaccent extension only allows replacing one source character
with one or more target characters. In Arabic, Hebrew and possibly other
languages, diacritics are standalone characters that are being added to
normal letters. To use unaccent dictionary for these languages, we need
Bruce Momjian writes:
> On Wed, Feb 26, 2014 at 10:21:03PM -0500, Tom Lane wrote:
>> Oh, I'd forgotten about that thread. I never particularly liked the patch
>> as presented: like Robert, I thought it far too complicated. My
>> inclination would just be to tweak the parser enough so that a simp
On Wed, Feb 26, 2014 at 10:21:03PM -0500, Tom Lane wrote:
> Noah Misch writes:
> > On Tue, Feb 25, 2014 at 01:15:09PM -0500, Tom Lane wrote:
> >> Really if we wanted to fix
> >> this issue we'd need to hack up transformAExprAnd/transformAExprOr so that
> >> they recognized nested ANDs/ORs and flat
On Sat, Apr 19, 2014 at 01:38:16PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > However, in the case of custom variables, you are right that pg_settings
> > doesn't show custom variables.
>
> That is entirely intentional: the reason we do not show placeholder
> variables in pg_settings is t
On Sat, Apr 19, 2014 at 3:37 AM, Bruce Momjian wrote:
>
> > One thing that I discussed with Merlin offline and am now concerned
> about is
> > how will the actual eviction work. We cannot traverse the entire list
> and then
> > find all the buffers with refcount 0 and then do another traversal to
Bruce Momjian writes:
> However, in the case of custom variables, you are right that pg_settings
> doesn't show custom variables.
That is entirely intentional: the reason we do not show placeholder
variables in pg_settings is that we have no accurate information about
them, and so everything pg_s
On Wed, Feb 12, 2014 at 03:54:31PM +0100, Stefan Seifert wrote:
> Hi!
>
> http://www.postgresql.org/docs/devel/static/sql-show.html claims:
> "Also, the pg_settings system view produces the same information."
>
> This is not entirely correct. On IRC I was told, that the view only contains
> sett
On Wed, Apr 16, 2014 at 11:01:56PM -0400, Bruce Momjian wrote:
> On Tue, Apr 1, 2014 at 10:32:01AM -0400, Tom Lane wrote:
> > Adrian Vondendriesch writes:
> > > I patched the function conninfo_array_parse() which is used by
> > > PQconnectStartParams to behave like PQsetdbLogin. The patch also
>
10 matches
Mail list logo
