On Wed, Nov 14, 2018 at 8:06 AM Sachin Kotwal wrote:
> Hi PostgreSQL lovers,
>
> I heard news that Redhat is going to acquired by IBM. IBM has its on
> database. And they have history of selling applications with their own
> hardware (software and hardware together).
>
> As per my knowledge
Hi PostgreSQL lovers,
I heard news that Redhat is going to acquired by IBM. IBM has its on
database. And they have history of selling applications with their own
hardware (software and hardware together).
As per my knowledge PostgreSQL community has better support for Redhat
family than any
On 11/13/18 3:47 PM, Rich Shepard wrote:
On Sun, 11 Nov 2018, Rich Shepard wrote:
Looks like the pg_dumpall '-h' option will act on the other host's data
directory.
Worked as advertised. Just read the dumped file into the new 11.1 data
directory.
Just realized the question I should have
On 11/13/18 4:41 PM, Rich Shepard wrote:
On Tue, 13 Nov 2018, Adrian Klaver wrote:
No:
" Each of the first four fields can be a literal value, or *, which
matches anything. "
Adrian,
Okay.
If the record starts with local then that is for socket connections.
If you are connecting to a
On Tue, 13 Nov 2018, Adrian Klaver wrote:
No:
" Each of the first four fields can be a literal value, or *, which matches
anything. "
Adrian,
Okay.
If the record starts with local then that is for socket connections.
If you are connecting to a host e.g -h localhost then you need to look
On 11/13/18 4:24 PM, Rich Shepard wrote:
On Tue, 13 Nov 2018, Adrian Klaver wrote:
You have two options:
1) The preferred one. Keep the password and create a .pgpass file to
hold the password:
https://www.postgresql.org/docs/10/libpq-pgpass.html
Adrian,
That's database-specific if I
On Tue, 13 Nov 2018, Adrian Klaver wrote:
You have two options:
1) The preferred one. Keep the password and create a .pgpass file to hold the
password:
https://www.postgresql.org/docs/10/libpq-pgpass.html
Adrian,
That's database-specific if I read the manual page correctly.
My guess
On 11/13/18 3:47 PM, Rich Shepard wrote:
On Sun, 11 Nov 2018, Rich Shepard wrote:
Looks like the pg_dumpall '-h' option will act on the other host's data
directory.
Worked as advertised. Just read the dumped file into the new 11.1 data
directory.
The new installation is asking for my
=?UTF-8?Q?R=C3=A9mi_Cura?= writes:
> So the pgpointcloud store sometimes very large groups of points into one
> row (TOASTED), something along few kB to few MB. TOAST would be in EXTERNAL
> mode (no compression).
> Sometimes we only want to access a part of this data (one or several blocks
>
Hi dear list,
I have a tricky question about TOASTED memory in Postgres related to the
[pgpointcloud](https://github.com/pgpointcloud/pointcloud) extension.
(using Postgres 11 if it matters)
So the pgpointcloud store sometimes very large groups of points into one
row (TOASTED), something along
On Sun, 11 Nov 2018, Rich Shepard wrote:
Looks like the pg_dumpall '-h' option will act on the other host's data
directory.
Worked as advertised. Just read the dumped file into the new 11.1 data
directory.
The new installation is asking for my password to access my databases.
Where do I
On 2018-Nov-13, Олег Самойлов wrote:
> Very much better. What about to copy paste algorithm from
> gin(jsonb_path_ops) to the hash index?
You're welcome to submit patches.
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training &
I am just doing experiment what a type a most suitable for enumeration in
PostgreSQL. And what index. And this effect looked for me very strange. There
is in the PostgreSQL one another hash index. This is gin(jsonb_path_ops) for
the jsob type. It is also use hash internally, but it is much
Am 13.11.2018 um 19:12 schrieb Ron:
On 11/13/2018 12:07 PM, Andreas Kretschmer wrote:
Am 13.11.2018 um 17:42 schrieb Олег Самойлов:
insert into gender (gender) select case when random<0.50 then
'female' when random<0.99 then 'male' else 'other' end from (select
random() as random,
Am 13.11.2018 um 17:42 schrieb Олег Самойлов:
insert into gender (gender) select case when random<0.50 then 'female'
when random<0.99 then 'male' else 'other' end from (select random() as
random, generate_series(1,:table_size)) as subselect;
is that really your intended data distibution?
On 11/13/2018 12:07 PM, Andreas Kretschmer wrote:
Am 13.11.2018 um 17:42 schrieb Олег Самойлов:
insert into gender (gender) select case when random<0.50 then 'female'
when random<0.99 then 'male' else 'other' end from (select random() as
random, generate_series(1,:table_size)) as subselect;
Олег Самойлов wrote:
> \set table_size 100
> begin;
> create table gender (gender varchar);
>
> insert into gender (gender) select case when random<0.50 then 'female' when
> random<0.99 then 'male' else 'other' end from (select random() as random,
> generate_series(1,:table_size)) as
CentOS 7
$ rpm -q postgresql10
postgresql10-10.6-1PGDG.rhel7.x86_64
SQL script for psql:
\set table_size 100
begin;
create table gender (gender varchar);
insert into gender (gender) select case when random<0.50 then 'female' when
random<0.99 then 'male' else 'other' end from (select
út 13. 11. 2018 v 16:42 odesílatel Pavel Demidov
napsal:
> Hello,
> Thank your answer. If there are a lot of messages 'LOG: incomplete startup
> packet' into postgres log will it cause the log overflow?
> Does it possible to filter it or ban to write.
>
It is garbage. Usually it means nothing,
>
> I apologize for top posting, Google hid all of the other stuff.
>
It is only me who thinks that when it comes to destroying email as a
communication tool, no one did a better job than effing gmail.
I apologize for top posting, Google hid all of the other stuff.
George
iGLASS Networks
www.iglass.net
>>
>>
CREATE OR REPLACE VIEW tickets AS
SELECT *, tableoid
FROM public.tickets
WHERE ( ticketsid IN (SELECT ticketsid
FROM machtick));
iGLASS Networks
www.iglass.net
On Tue, Nov 13, 2018 at 10:32 AM Adrian Klaver
wrote:
> On 11/13/18 6:54 AM, George
Hello,
Thank your answer. If there are a lot of messages 'LOG: incomplete startup
packet' into postgres log will it cause the log overflow?
Does it possible to filter it or ban to write.
Regards,
Paul
On Thu, Nov 8, 2018 at 1:06 PM Pavel Stehule
wrote:
> Hi
>
> čt 8. 11. 2018 v 10:19
On 11/13/18 6:54 AM, George Woodring wrote:
The tickets view restricts which tickets can be seen by the schema.
9.3 must have created the view in the same column order as the table
(which is the case looking at one of our 9.3 databases which we have not
updated yet), which is why we never saw
The tickets view restricts which tickets can be seen by the schema.
9.3 must have created the view in the same column order as the table (which
is the case looking at one of our 9.3 databases which we have not updated
yet), which is why we never saw the issue before.
George
iGLASS Networks
On 11/13/18 6:27 AM, George Woodring wrote:
I think the issue is that the function is not putting the data into the
tickets%ROWTYPE correctly. When I do \d on public.tickets and
iss-hackers.tickets, the columns are in a different order.
The error message is saying column2 is not a
On 11/13/18 6:27 AM, George Woodring wrote:
I think the issue is that the function is not putting the data into the
tickets%ROWTYPE correctly. When I do \d on public.tickets and
iss-hackers.tickets, the columns are in a different order.
That is because you have a table tickets in the public
On 11/13/18 1:12 AM, Om Prakash Jaiswal wrote:
I am using postgresql 10.6
While restore data using psql, error getting literal carriage return
found line no. 4446578 hint use \r
Can you show the entire row(line)?
I used \i and \r , still getting same error.
Backup size 35GB plain databack
I think the issue is that the function is not putting the data into the
tickets%ROWTYPE correctly. When I do \d on public.tickets and
iss-hackers.tickets, the columns are in a different order.
\d public.tickets
Column| Type |
Modifiers
On 11/13/18 5:17 AM, George Woodring wrote:
We are having an issue with one of our plpgsql functions after migrating
from 9.3 to 9.6. The function works fine until you change the search path.
psql (9.6.10)
Type "help" for help.
woody=> select ticket_summary(8154);
Hi
út 13. 11. 2018 v 14:18 odesílatel George Woodring <
george.woodr...@iglass.net> napsal:
> We are having an issue with one of our plpgsql functions after migrating
> from 9.3 to 9.6. The function works fine until you change the search path.
>
> psql (9.6.10)
> Type "help" for help.
>
>
We are having an issue with one of our plpgsql functions after migrating
from 9.3 to 9.6. The function works fine until you change the search path.
psql (9.6.10)
Type "help" for help.
woody=> select ticket_summary(8154);
ticket_summary
Hi,
You might have to wait for pg_is_in_recovery to be false after the
promotion. (in 9.6 pg_ctl promote doesn't wait for promotion to complete
unlike 10). [1]
You should CHECKOINT between 2 and 3. (or wait for the first checkpoint to
finish)
In the thread [2], Michael Paquier explains that:
"
I am using postgresql 10.6While restore data using psql, error getting literal
carriage return found line no. 4446578 hint use \r I used \i and \r , still
getting same error.Backup size 35GB plain databack up.Data type JSON in which I
am getting error while copy ing in restore operation.
34 matches
Mail list logo
