Hello All,
We have newbie to Postgresql.
Background:
We have site hosted on Ruby on Rails using Postgresql database.It is a
eCommerce site and for which we need to provide the NLS supported Search
functionality to help end users while searching by using Synonyms, related word
, Plurals and Sing
Hi,
quick question regarding
https://wiki.postgresql.org/wiki/May_2015_Fsync_Permissions_Bug
Will 9.4.3 be exactly like 9.4.2 except for the permission
bug, or will there be other fixes too?
Bye,
Chris.
PS: yes, I've read the section "Should I not apply the updates?".
--
Sent via pgsql-ge
Hi,
On Thu, 2015-05-28 at 10:37 +0200, Chris Mair wrote:
> Will 9.4.3 be exactly like 9.4.2 except for the permission
> bug, or will there be other fixes too?
There are a few more fixes available in the queue, including another
multixact fix.
Regards,
--
Devrim GÜNDÜZ
Principal Systems Enginee
OS . Fedora 22. It is my localhost.
website : enl.global.
for phppgadmin : phppgadmin.enl.global
Nginx, php, postgresql
socket:
--
bash-4.3# ls -al /run/postgresql/
srwxrwxrwx 1 postgres postgres 0 May 28 10:10 .s.PGSQL.5432
-rw--- 1 postgres postgres 52 May 28
On 15/05/28 17:55, arnaud gaboury wrote:
(...)
> I can't log from the phppgadmin. I have login failed.
> First, I am not sure if I shall log with my unix account or postgres
> role (I guess the latter one).
>
> Log:
> LOG: database system is ready to accept connections
> LOG: connection received
On Thu, May 28, 2015 at 11:04 AM, Ian Barwick wrote:
> On 15/05/28 17:55, arnaud gaboury wrote:
> (...)
>> I can't log from the phppgadmin. I have login failed.
>> First, I am not sure if I shall log with my unix account or postgres
>> role (I guess the latter one).
>>
>> Log:
>> LOG: database sy
>> Will 9.4.3 be exactly like 9.4.2 except for the permission
>> bug, or will there be other fixes too?
>
> There are a few more fixes available in the queue, including another
> multixact fix.
Ok,
good to know, thanks!
Bye,
Chris.
--
Sent via pgsql-general mailing list (pgsql-general@po
Hi everybody,
what do I need to do in order to enable compound word handling in
PostgreSQL tsvector implementation?
I run an Ubuntu 14.04 machine, PostgreSQL 9.3, have installed package
hunspell-de-de and already created a new dictionary as described here:
http://www.postgresql.org/docs/9.3/
On Wed, May 27, 2015 at 6:21 PM, Alvaro Herrera
wrote:
> Steve Kehlet wrote:
>> I have a database that was upgraded from 9.4.1 to 9.4.2 (no pg_upgrade, we
>> just dropped new binaries in place) but it wouldn't start up. I found this
>> in the logs:
>>
>> waiting for server to start2015-05-27 1
On Wed, May 27, 2015 at 6:21 PM, Alvaro Herrera
wrote:
> Steve Kehlet wrote:
>> I have a database that was upgraded from 9.4.1 to 9.4.2 (no pg_upgrade, we
>> just dropped new binaries in place) but it wouldn't start up. I found this
>> in the logs:
>>
>> waiting for server to start2015-05-27 1
On Thu, May 28, 2015 at 8:01 AM, Robert Haas wrote:
> On Wed, May 27, 2015 at 6:21 PM, Alvaro Herrera
> wrote:
>> Steve Kehlet wrote:
>>> I have a database that was upgraded from 9.4.1 to 9.4.2 (no pg_upgrade, we
>>> just dropped new binaries in place) but it wouldn't start up. I found this
>>> i
On Thu, May 28, 2015 at 8:03 AM, Robert Haas wrote:
>> Steve, is there any chance we can get your pg_controldata output and a
>> list of all the files in pg_clog?
>
> Err, make that pg_multixact/members, which I assume is at issue here.
> You didn't show us the DETAIL line from this message, which
Sorry,
The query run times are significantly slower on outdb as that using indb
here are the run times on 2 queries.
ST_Count/ST_Clip(select single band here)/Inner Join/ST_Transform (US
Counties)
OutDB: 873.564s (14 minutes 33s) InDB: 127.36s (2 minutes 7s)
ST_Count(select single band here
I am testing partitioning of a large table. I am INHERITING child tables.
It is using a range
partitioning based on a sequence col, which also acts as the primary
key. For inserts I am using a trigger which will redirect insert to
the right table based on the value of the primary key.
Based on my
ts_debug() ?
=# select * from ts_debug('english', 'messages');
alias | description | token | dictionaries | dictionary |
lexemes
---+-+--++--+--
asciiword | Word, all ASCII | messages | {english_stem} | english_st
Sure. Here you are:
=# select ts_debug('public.german_compound', 'wasserkraft');
ts_debug
-
(asciiword,"Word, all
ASCII",wasserkraft,"{german_hunspell,german_stem}",german_stem,{wasserkraft})
=
Hey thanks for the help !
> > Hey dear List,
> >
> > On a windows XP 64.
> >
> > I installed python (64b),
> > it works.
>
> What version of Python 2 or 3 or both?
>
> What does python -V show at the command line?
>
Python 3.2 and python 2.6, both 64bits are installed on the PC.
Whe
> Have you set up constraints on the partitions? The planner needs to know
> what is in the child tables so it can avoid scanning them.
Yes. each child table is defined as follows
CREATE TABLE TSTESTING.ACCOUNT_PART1
( CHECK (ACCOUNT_ROW_INST BETWEEN 1001 and 271660))
INHERITS (TSTESTING.ACCO
Am 28. Mai 2015 17:15:22 MESZ, schrieb Ravi Krishna :
>I am testing partitioning of a large table. I am INHERITING child
>tables.
>It is using a range
>partitioning based on a sequence col, which also acts as the primary
>key. For inserts I am using a trigger which will redirect insert to
>the ri
Generally, when you partition, data should only be in child tables, and the
parent table should be empty, otherwise you defeat the purpose of
parttioning.`
On Thu, May 28, 2015 at 12:25 PM, Ravi Krishna
wrote:
> > Have you set up constraints on the partitions? The planner needs to know
> > what
Am 28. Mai 2015 18:25:42 MESZ, schrieb Ravi Krishna :
>> Have you set up constraints on the partitions? The planner needs to
>know
>> what is in the child tables so it can avoid scanning them.
>
>Yes. each child table is defined as follows
>
>CREATE TABLE TSTESTING.ACCOUNT_PART1
>
> ( CHECK (ACCO
Ravi Krishna writes:
> Perhaps I was not clear. The planner is excluding partitions which can
> not contain the rows looked up in the WHERE clause. However it is
> still scanning the parent table.
Sure, because you don't have a constraint forbidding the parent from
having a matching row, no?
In
On Thu, May 28, 2015 at 12:42 PM, Melvin Davidson wrote:
>
> Generally, when you partition, data should only be in child tables, and the
> parent table should be empty, otherwise you defeat the purpose of
> parttioning.`
yes of course the parent table is empty. The trigger on insert is
redirect
I'm trying to setup streaming replication but I'm stuck, please help!
I followed the steps in
https://wiki.postgresql.org/wiki/Streaming_Replication
On Master I have (postgresql.conf)
archive_mode = on
wal_level = archive
max_wal_senders = 5
wal_keep_senders = 150
(pg_hba.conf)
host replicatio
On 05/28/2015 09:56 AM, Ivann Ruiz wrote:
I'm trying to setup streaming replication but I'm stuck, please help!
autovacuum launcher started|
And then nothing else happens, please I really need help with this, I
appreciate all comments. Any questions, please feel free to ask.
I would like
> By and large, though, this doesn't really matter, since an empty
> parent table won't cost anything much to scan. If it's significant
> relative to the child table access time then you probably didn't
> need partitioning in the first place.
Is there a rule of thumb as to at what size does the p
On Thu, May 28, 2015 at 12:50 PM, Tom Lane wrote:
> Sure, because you don't have a constraint forbidding the parent from
> having a matching row, no?
As suggested by you, I included a bogus condition in the parent table
which will prevent any row addition in the parent table and made the
constra
Ravi Krishna writes:
> Is there a rule of thumb as to at what size does the partitioning
> start performing better than non partitioned table.
Personally I'd not worry about partitioning until I had a table
approaching maybe a billion (1e9) rows. You could argue that
an order of magnitude either
On May 28, 2015 9:58 AM, "Ivann Ruiz" wrote:
> When I execute pg_ctl start on my standby I get the following
>
> LOG: database system was interrupted; last known up at 2015-05-27
14:16:41 EDT
> LOG: entering standby mode
> LOG: restored log file "00010028" from archive
> LOG:
Ravi Krishna writes:
> So cost wise they both look same, still when i run the sql in a loop
> in large numbers, it takes rougly 1.8 to 2 times more than non
> partitioned table.
If you're testing cases that only involve fetching a single row,
the discrepancy could well be down to extra planning
> On 28 May 2015, at 17:54, Rémi Cura wrote:
>
> I tried:
>
> C:\Python32>python.exe
>
> Python 3.2 (r32:88445, Feb 20 2011, 21:30:00) [MSC v.1500 64 bit (AMD64)] on
> win32
Ehm, this seems significant?
---^
It looks l
On Thu, May 28, 2015 at 8:51 AM, Robert Haas wrote:
> [ speculation ]
OK, I finally managed to reproduce this, after some off-list help from
Steve Kehlet (the reporter), Alvaro, and Thomas Munro. Here's how to
do it:
1. Install any pre-9.3 version of the server and generate enough
multixacts to
On 05/28/2015 12:56 PM, Robert Haas wrote:
FTR: Robert, you have been a Samurai on this issue. Our many thanks.
Sincerely,
jD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended"
I have been using UUIDs for PKs to allow me the flexibility of
generating PKs within PostgreSQL or at the application code level.
However, I have been storing them as CHAR(32) in the hex string
representation (no dashes) in order to simplify comparisons and
manipulations at a very practical level.
Robert Haas wrote:
> On Thu, May 28, 2015 at 8:51 AM, Robert Haas wrote:
> > [ speculation ]
>
> OK, I finally managed to reproduce this, after some off-list help from
> Steve Kehlet (the reporter), Alvaro, and Thomas Munro. Here's how to
> do it:
It's a long list of steps, but if you consider
On Fri, May 29, 2015 at 7:56 AM, Robert Haas wrote:
> On Thu, May 28, 2015 at 8:51 AM, Robert Haas wrote:
>> [ speculation ]
>
> [...] However, since
> the vacuum did advance relfrozenxid, it will call vac_truncate_clog,
> which will call SetMultiXactIdLimit, which will propagate the bogus
> dat
On Thu, May 28, 2015 at 4:06 PM, Joshua D. Drake wrote:
> FTR: Robert, you have been a Samurai on this issue. Our many thanks.
Thanks! I really appreciate the kind words.
So, in thinking through this situation further, it seems to me that
the situation is pretty dire:
1. If you pg_upgrade to 9
On 5/18/15 10:52 AM, Filipe Pina wrote:
> But one of the functions I need to create needs to accept an array of
> records.
PL/Python doesn't support that. Some more code needs to be written to
support that. You did everything correctly. I don't know of a good
workaround.
--
Sent via pgsql-g
On 5/28/15 5:35 PM, Randall Lucas wrote:
> Can I compile my own version of uuid_out and update the system
> catalogs, or create a "uuid_dashless" type that uses my own custom
> uuid_dashless.c that's hacked to remove dashes?
Either one would work.
--
Sent via pgsql-general mailing list (pgsql-
On 05/28/2015 08:54 AM, Rémi Cura wrote:
Hey thanks for the help !
> Hey dear List,
>
> On a windows XP 64.
>
> I installed python (64b),
> it works.
What version of Python 2 or 3 or both?
What does python -V show at the command line?
Python 3.2 and python 2.
Robert Haas wrote:
> 2. If you pg_upgrade to 9.3.7 or 9.4.2, then you may have datminmxid
> values which are equal to the next-mxid counter instead of the correct
> value; in other words, they are too new.
What you describe is what happens if you upgrade from 9.2 or earlier.
For this case we use
Alvaro Herrera wrote:
> Robert Haas wrote:
>
> > 2. If you pg_upgrade to 9.3.7 or 9.4.2, then you may have datminmxid
> > values which are equal to the next-mxid counter instead of the correct
> > value; in other words, they are too new.
>
> What you describe is what happens if you upgrade from 9
On Thu, May 28, 2015 at 10:41 PM, Alvaro Herrera
wrote:
>> 2. If you pg_upgrade to 9.3.7 or 9.4.2, then you may have datminmxid
>> values which are equal to the next-mxid counter instead of the correct
>> value; in other words, they are too new.
>
> [ discussion of how the control file's oldestMul
43 matches
Mail list logo
