I have a database with a rather large events table defined something
like:
# create table events(a int4, b int4, primary key(b,a));
CREATE TABLE
There are more columns, but thy are not relevent here. What I do have
is 7(!) tables that reference this one like so:
# create table attr1(a int4, b in
Thank-you all... create extension hstore; was exactly what I needed (I'm
new to PostgreSQL and was unfamiliar with the terminology... was searching
unsuccessfully for things like "install hstore module").
Joey
On Wed, Nov 20, 2013 at 4:12 PM, Joey Quinn wrote:
> I'm using 9.3 (Windows 64 bit)
>
> From: Tom Lane
>To: Paul Jones
>Cc: "pgsql-general@postgresql.org"
>Sent: Wednesday, November 20, 2013 9:13 AM
>Subject: Re: [GENERAL] Debugging extension with gdb?
>
>
>Paul Jones writes:
>
>> Can someone point me to information on how to debug a Postgres
On 11/20/2013 1:12 PM, Joey Quinn wrote:
I'm using 9.3 (Windows 64 bit) and would like to use an hstore field
in new table but it does not appear to be available. How do I add the
correct module?
CREATE EXTENSION hstore;
should install the hstore contributed module into the current dat
Here you go:
http://www.postgresql.org/docs/current/static/hstore.html#HSTORE-OP-TABLE
On Thu, Nov 21, 2013 at 2:42 AM, Joey Quinn wrote:
> I'm using 9.3 (Windows 64 bit) and would like to use an hstore field in
> new table but it does not appear to be available. How do I add the correct
> modu
On Wed, Nov 20, 2013 at 04:07:59PM +0100, Karsten Hilbert wrote:
> > On Wed, Nov 20, 2013 at 02:36:08PM +0100, Karsten Hilbert wrote:
> > > > Karsten Hilbert wrote:
> > > > > Let me try to rephrase:
> > > > >
> > > > > Fact: pg_upgrade can NOT properly upgrade clusters which contain
> > > > >
I'm using 9.3 (Windows 64 bit) and would like to use an hstore field in new
table but it does not appear to be available. How do I add the correct
module?
Joey
I've read that setting LC_COLLATE to something other than "C" / "POSIX"
negatively affects performance, and disables use of indexes for LIKE, etc...
Does the same apply to LC_CTYPE?
I am considering setting LC_COLLATE = "C", and LC_CTYPE = "en_US.UTF-8", and
using LOWER() to case-fold strings f
On Mon, Nov 18, 2013 at 5:39 PM, Stefan Keller wrote:
> Hi Jeff and Martin
>
> On 18. November 2013 17:44 Jeff Janes wrote:
> > I rather doubt that. All the bottlenecks I know about for well cached
> read-only workloads are around
> > locking for in-memory concurrency protection, and have littl
On 11/20/2013 10:21 AM, gajendra s v wrote:
Hi All,
I need to change content of xml ,Please any one suggest me how to
do,the xml is below
FailValue="0"/>2534Value="1"/>99432Value="2"/>43232Value="3"/>43323Value="4"/>33432Value="5"/>453432
I want xml like below,is there any way
'*Pass*Va
Hi All,
I need to change content of xml ,Please any one suggest me how to do,the
xml is below
Fail253499432432324332333432453432
I want xml like below,is there any way
'*Pass**40*3499432432324332333432453432
Hi Bruce
2013/11/20 Bruce Momjian
> On Sun, Nov 17, 2013 at 09:00:05PM +0900, Michael Paquier wrote:
> > On Sun, Nov 17, 2013 at 8:25 PM, Stefan Keller
> wrote:
> > > How can Postgres be used and configured as an In-Memory Database?
> > >
> > > Does anybody know of thoughts or presentations abo
On Tue, Nov 19, 2013 at 7:41 PM, Edson Richter wrote:
>
>
> Ok, I still have one doubt (I'm learning a lot, tkx!):
>
> What happens, then, if data has been commited (so it is in xlog), but it
> is not in data pages yet, and it doesn't fit in memory buffers anymore: how
> would PostgreSQL query dat
Paul Jones writes:
> Can someone point me to information on how to debug a Postgres extension
> with gdb?
I've noticed that on some platforms, it works better to attach gdb to the
backend process before you load the extension, but on others, it works
better to attach afterwards. You might try t
> On Wed, Nov 20, 2013 at 02:36:08PM +0100, Karsten Hilbert wrote:
> > > Karsten Hilbert wrote:
> > > > Let me try to rephrase:
> > > >
> > > > Fact: pg_upgrade can NOT properly upgrade clusters which contain
> > > > databases that are set to "default_transaction_read_only on"
> > > >
> > >
On Wed, Nov 20, 2013 at 02:36:08PM +0100, Karsten Hilbert wrote:
> > Karsten Hilbert wrote:
> > > Let me try to rephrase:
> > >
> > > Fact: pg_upgrade can NOT properly upgrade clusters which contain
> > > databases that are set to "default_transaction_read_only on"
> > >
> > > Question: Is
Can someone point me to information on how to debug a Postgres extension
with gdb?
I have been able to attach to one but getting breakpoints to work right
and getting the addresses to properly relocate (since the extension
could be loaded anywhere) has been the problem for me.
I have not found
> Karsten Hilbert wrote:
> > Let me try to rephrase:
> >
> > Fact: pg_upgrade can NOT properly upgrade clusters which contain
> > databases that are set to "default_transaction_read_only on"
> >
> > Question: Is this intended ?
>
> I am pretty sure that this is an oversight and hence a bug
Karsten Hilbert wrote:
> Let me try to rephrase:
>
> Fact: pg_upgrade can NOT properly upgrade clusters which contain
> databases that are set to "default_transaction_read_only on"
>
> Question: Is this intended ?
I am pretty sure that this is an oversight and hence a bug.
Yours,
Laurenz
> On Tue, Nov 19, 2013 at 11:22:47AM +0100, Karsten Hilbert wrote:
> > ERROR: transaction is read-only
> >
> > Now, this is quite understandable since one of the databases
> > is set to
> >
> > ALTER DATABASE ... SET DEFAULT_TRANSACTION_READ_ONLY TO ON;
> >
> > However, since the above
On Tue, Nov 19, 2013 at 11:22:47AM +0100, Karsten Hilbert wrote:
> ERROR: transaction is read-only
>
> Now, this is quite understandable since one of the databases
> is set to
>
> ALTER DATABASE ... SET DEFAULT_TRANSACTION_READ_ONLY TO ON;
>
> However, since the above setting is som
On Sun, Nov 17, 2013 at 09:00:05PM +0900, Michael Paquier wrote:
> On Sun, Nov 17, 2013 at 8:25 PM, Stefan Keller wrote:
> > How can Postgres be used and configured as an In-Memory Database?
> >
> > Does anybody know of thoughts or presentations about this "NoSQL feature" -
> > beyond e.g. "Perspe
22 matches
Mail list logo
