Thanks, problem was mine, all is ok now, thanks.
I were putting es_ES@iso885915 or es_ES@latin9 and it wasn't working ..
Solution was using es_ES.iso885915@euro for collation and ctype (and latin9
for encoding).
Thanks to all!
Regards...
2015-02-10 23:26 GMT+00:00 Jeremiah Ocasio <
joca...@kaleid
Sorry, it took me a while to respond, but I re-factored all of this process
to suggestions.
On Wed, Jan 7, 2015 at 7:49 PM, Maxim Boguk wrote:
>
> On Wed, Jan 7, 2015 at 8:49 PM, Pawel Veselov
> wrote:
>>
>> PS: your setup look pretty complicated and hard to analyze without seeing
>>> all involv
I am currently planning to set up a PostgreSQL + PostGIS instance for my
lab. Turns out I believe this would be useful for the whole center, so
that I'm now considering setting up the server for everyone—if interest
is shared of course. At the moment, I am however struggling with what
would be req
On 11/02/15 13:52, Mathieu Basille wrote:
Dear PostgreSQL users,
I am posting here a question that I initially asked on the PostGIS
list [1], where I was advised to try here too (I will keep both lists
updated about the developments on this issue).
I am currently planning to set up a Postgre
Responses in-line:
On Tue, 10 Feb 2015 19:52:41 -0500
Mathieu Basille wrote:
>
> I am posting here a question that I initially asked on the PostGIS list
> [1], where I was advised to try here too (I will keep both lists updated
> about the developments on this issue).
>
> I am currently plan
Dear PostgreSQL users,
I am posting here a question that I initially asked on the PostGIS list
[1], where I was advised to try here too (I will keep both lists updated
about the developments on this issue).
I am currently planning to set up a PostgreSQL + PostGIS instance for my
lab. Turns o
There was no reason I needed to run full statements in this case. I just
didn't know I could get the type ids like that.
Thanks for all of your help Andres!
On Tue, Feb 10, 2015 at 1:23 PM, Andres Freund
wrote:
> On 2015-02-10 10:33:41 -0800, Xavier Stevens wrote:
> > Sorry to raise the issue
Hello Adrian,
Not sure if this is what your looking for insofar as a solution but have
you taken a look at this page from the documentation.
http://www.postgresql.org/docs/9.3/static/multibyte.html
On Mon, Feb 9, 2015 at 12:11 AM, Oliver wrote:
> 2015-02-09 7:52 GMT+00:00 Oliver :
>
>> 2015-
On 2015-02-10 10:33:41 -0800, Xavier Stevens wrote:
> Sorry to raise the issue on startup_cb. I added a whole bunch of logging
> statements and I was only running the section of code I wanted when the
> startup callback had options.
Heh.
Just to make sure: You can pass options via replication pro
On Mon, Feb 9, 2015 at 3:07 AM, David Evans wrote:
> On 9 February 2015 at 03:57, Gavin Flower
> wrote:
>>
>> Would using jsonb be more consistent?
>
>
> Yes, casting to jsonb seems produce consistent output:
>
> # SELECT array_to_json(array[1, 2, 3])::jsonb, json_build_array(1, 2,
> 3)::jsonb;
On Tue, 10 Feb 2015 13:02:05 -0600
Felipe Gasper wrote:
> On 2/10/15 12:57 PM, David G Johnston wrote:
> > Felipe Gasper wrote
> >> Is there a quick way to reset a PgSQL cluster to its pristine
> >> state--i.e., to what initdb gives but preserving configuration
> >> customizations?
> >
> > Not th
On 2/10/2015 11:02 AM, Felipe Gasper wrote:
On 2/10/15 12:57 PM, David G Johnston wrote:
Felipe Gasper wrote
Is there a quick way to reset a PgSQL cluster to its pristine
state--i.e., to what initdb gives but preserving configuration
customizations?
Not that I am aware of.
If you describe yo
On 10/02/2015 19:02, Felipe Gasper wrote:
> On 2/10/15 12:57 PM, David G Johnston wrote:
>> Felipe Gasper wrote
>>> Is there a quick way to reset a PgSQL cluster to its pristine
>>> state--i.e., to what initdb gives but preserving configuration
>>> customizations?
>>
>> Not that I am aware of.
>>
>
On 02/10/2015 10:49 AM, Felipe Gasper wrote:
Hello,
Is there a quick way to reset a PgSQL cluster to its pristine
state--i.e., to what initdb gives but preserving configuration
customizations?
Something like:
cp -r /pgdata to pgdata_bak/ at initial state.
When you want to reset cp -r pg
On 2/10/2015 10:49 AM, Felipe Gasper wrote:
Is there a quick way to reset a PgSQL cluster to its pristine
state--i.e., to what initdb gives but preserving configuration
customizations?
backup the .conf file(s), initdb, restore the .conf files.
--
john r pierce
On 2/10/15 12:57 PM, David G Johnston wrote:
Felipe Gasper wrote
Is there a quick way to reset a PgSQL cluster to its pristine
state--i.e., to what initdb gives but preserving configuration
customizations?
Not that I am aware of.
If you describe your use-case then meaningful suggestions could
Felipe Gasper wrote
> Is there a quick way to reset a PgSQL cluster to its pristine
> state--i.e., to what initdb gives but preserving configuration
> customizations?
Not that I am aware of.
If you describe your use-case then meaningful suggestions could be offered.
David J.
--
View this m
Hello,
Is there a quick way to reset a PgSQL cluster to its pristine
state--i.e., to what initdb gives but preserving configuration
customizations?
Thank you!
-FG
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www
Sorry to raise the issue on startup_cb. I added a whole bunch of logging
statements and I was only running the section of code I wanted when the
startup callback had options.
This now gets me to the next issue I encounter. In my output plugin, I'm
trying to use the SPI interface to query about Pos
Adrian, in response to your question:
> 2015-02-06 07:11:38 EST FATAL: le rôle « 208375PT$ » n'existe pas
>
So where is role 208375PT$ supposed to come from?
I found that when I stop/start/restart pgsql through the services.msc
application in Windows, this message is issued in the log file. Th
Hi Thomas,
The partial unique index would prevent multiple person records with the
same email. I want to allow that as long as they agree on the value of
user.
Kai
On Tue, Feb 10, 2015 at 2:14 AM, Thomas Kellerer wrote:
> Kai Groner schrieb am 10.02.2015 um 01:38:
> > Given the following ta
On Tue, Feb 10, 2015 at 5:59 PM, Andres Freund
wrote:
> On 2015-02-10 11:01:08 +0900, Michael Paquier wrote:
>> Just in case, I have just done a quick test with pg_recvlogical on
>> latest HEAD of REL9_4_STABLE and the startup_cb gets called:
>> DEBUG: received replication command: IDENTIFY_SYSTE
Hi,
we recently found a bug in one of our applications which was doing exactly the
same UPDATE operation a few thousand times inside a transaction. This caused
the UPDATEs to become slower and slower from some milliseconds to some seconds.
We already fixed the application but I am wondering i
On 2015-02-10 11:01:08 +0900, Michael Paquier wrote:
> Just in case, I have just done a quick test with pg_recvlogical on
> latest HEAD of REL9_4_STABLE and the startup_cb gets called:
> DEBUG: received replication command: IDENTIFY_SYSTEM
> DEBUG: received replication command: START_REPLICATION
Hi,
On 2015-02-09 16:52:59 -0800, Xavier Stevens wrote:
> I'm trying to write a logical decoding plugin and I'm seeing some
> interesting behavior around the startup callback. When I use psql and the
> built-in SQL functions (like pg_logical_slot_peek_changes) to use my module
> I see the startup_
25 matches
Mail list logo
