If you can do this one without unnesting the downloads array I do not know how.
Having done that: (WHERE dlarray->'publd' = '123)
I think it’s doable like this:
select * from contacts where data @> '{"downloads":[{"pubid":123}]}'::jsonb
…which would be aided by a gin index on ‘data’ using json
Hi,
I'am going to try resolving slow buffer mappings by enabling huge pages (and in
general it looks like some MMU/TLB overhead takes place on server with 192GB
RAM and 48GB shared buffers, PG96). Please assist in understanding some details.
1. Does it mean that dirtying several 8kb buffers in
Thanks Thomas.
Still fancying the manual approach litlle bit more.
Will probably go with 8 database and 32 schema per machine. This way, will
keep in limits for administration tools as well as autovacuum, also will be
ready for connection pooling, as 8 databases is not to much.
This will give us
Andreas Kretschmer and others of the german mailing list put me on the
right track again. My working config changes from standard is as listed
below. My problem was, that application_name in primary_conninfo of the
standby was missing. This lead the master not to recognise standby
having taken
Oh, I forgot again already. *shame on me*
I tried to set up streaming replication without cloning standby from the
master by pg_basebackup. This lead to the error of unequal identifier
error. Maybe I was not reading carefully enough, however, I was not sure
what to do with the created files an
Hi,
I'm considering changing my database schema upgrade routines to recreate
functions and all objects depending on them (e.g. triggers, views) just after
the database server is started. It would make the routines much simpler since
they wouldn't have to depend on the history of the schema.
Does
On 31/01/2018 14:45, Konrad Witaszczyk wrote:
Hi,
I'm considering changing my database schema upgrade routines to recreate
functions and all objects depending on them (e.g. triggers, views) just after
the database server is started. It would make the routines much simpler since
they wouldn't hav
On 01/31/2018 14:03, Achilleas Mantzios wrote:
> On 31/01/2018 14:45, Konrad Witaszczyk wrote:
>> Hi,
>>
>> I'm considering changing my database schema upgrade routines to recreate
>> functions and all objects depending on them (e.g. triggers, views) just after
>> the database server is started. It
On 31/01/2018 15:22, Konrad Witaszczyk wrote:
On 01/31/2018 14:03, Achilleas Mantzios wrote:
On 31/01/2018 14:45, Konrad Witaszczyk wrote:
Hi,
I'm considering changing my database schema upgrade routines to recreate
functions and all objects depending on them (e.g. triggers, views) just after
On 01/31/2018 14:32, Achilleas Mantzios wrote:
> On 31/01/2018 15:22, Konrad Witaszczyk wrote:
>> On 01/31/2018 14:03, Achilleas Mantzios wrote:
>>> On 31/01/2018 14:45, Konrad Witaszczyk wrote:
Hi,
I'm considering changing my database schema upgrade routines to recreate
functio
> On 30 Jan 2018, at 12:32, Findlay, Thomas C
> wrote:
>
> Hello,
>
> How do you load GIS shapefiles into a pgAdmin database, using pgAdmin 4?
>
> I have done this in pgAdmin 3 using the PostGIS Shapefile loader, but can’t
> seem to find this in version 4.
In case noone here knows the ans
No. It's because your view's WHERE clause is being added to your INSERT
and of course nothing matches, so nothing gets inserted.
> That would fit with what I observe, but I’m not sure how I go about
> proving
EXPLAIN
Thanks. You’re right - I should have thought to use EXPLAIN before posting here.
On Wed, Jan 31, 2018 at 8:39 AM, Steven Winfield <
steven.winfi...@cantabcapital.com> wrote:
>
> Don't use RULEs.
> --
> Vik Fearing +33 6 46 75 15 36 <+33%206%2046%2075%2015%2036>
> http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
>
>
>
>
>
> Repeating this, as if I should alrea
On 31/01/2018 18:02, David G. Johnston wrote:
On Wed, Jan 31, 2018 at 8:39 AM, Steven Winfield mailto:steven.winfi...@cantabcapital.com>>wrote:
Don't use RULEs.
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
Repeating
On 01/31/18 13:26, Thiemo Kellner wrote:
master by pg_basebackup. This lead to the error of unequal identifier
error. Maybe I was not reading carefully enough, however, I was not sure
Addendum: The error shows up in the standby log.
--
+49 (0)1578-772 37 37
+41 (0)78 947 36 21
SIP/iptel.org:
Hello,
I have a question for postgres hardware requirement for production
installation. My org want to use Vms with only 8 cores max + 64Gb RAM max.
I have 4 database out of which 1 Db is write extensive 1 db is read
extensive and moderate write and 2 other DBs are read with write one.
can someone
How much data do you have? That’s a fundamental thing to know.
Martin.
From: Azimuddin Mohammed
Date: Wednesday, 31 January 2018 at 16:24
To: ,
Subject: postgres for production
Hello,
I have a question for postgres hardware requirement for production
installation. My org want to
Not really with only that information. There's a lot more to running any
database in a virtualized environment.
Additionally, 8 cores max? Well, how long does a read or a write take? Are
these complex SELECTs with multiple joins of millions of rows that return in
30s or 1m? If so, do you have
thanks for the reply scott.
The reads are pretty quick, we will use pg for reading/storing metadata
information only. not complex joins run, and the 4 dbs are of different
size , each db around 200 GB max total
On Wed, Jan 31, 2018 at 10:28 AM, Scott Whitney wrote:
> Not really with only that i
On 2018-01-31 10:23:58 -0600, Azimuddin Mohammed wrote:
> I have a question for postgres hardware requirement for production
> installation. My org want to use Vms with only 8 cores max + 64Gb RAM max. I
> have 4 database out of which 1 Db is write extensive 1 db is read extensive
> and
> moderate
If a table is set to unlogged is it inherently non-durable? That, is any
crash or unsafe shutdown _must_ result in truncation upon recovery?
I can imagine a table that is bulk loaded in a warehousing scenario and
then sitting statically could be safe, but maybe the question becomes how
could the s
Create a user and schema of same name with in ‘abc’ db through linux shell –
Psql steps---
1> [/home]# su postgres
2> bash-4.1$ psql
3> postgres=# \c abc [ set database abc]
4> abc=# create user abhra with password ‘1234’
5> abc=# alter user abhra with superuser
6> abc=# create s
On Wed, Jan 31, 2018 at 10:27:53PM +0530, Abhra Kar wrote:
> Create a user and schema of same name with in ‘abc’ db through linux shell –
>
>
>
> Psql steps---
>
>
>
> 1> [/home]# su postgres
>
> 2> bash-4.1$ psql
>
> 3> postgres=# \c abc [ set database abc]
>
> 4> abc=# create user
> That very much depends on where exactly the failure happens - it might
> be both (or relying on an assumption that changed over). It's not clear
> if it fails during query execution or formatting the output (I seem to
> remember there were/are issues with rows containing multiple large bytea
> v
On 2018-01-04 13:47:49 -0800, Mana M wrote:
> I was thinking about dumping everything into TEMP table and using that
> as source for INSERT ... ON CONFLICT. However, I was not sure on how
> to get thousands of rows from my Python application into TEMP table in
> one shot. Or is there any better alt
Thank you Peter!, I will check DNS configuration.
Regards
Jorge
-Original Message-
From: EXTERNAL:Peter Eisentraut [mailto:peter.eisentr...@2ndquadrant.com]
Sent: miércoles, 31 de enero de 2018 01:33 a.m.
To: HIRTZ Jorge Alberto TENARIS ;
pgsql-general@lists.postgresql.org
Subject: Re:
Hi,
We've experienced a DB incident related to WAL. The issue is now somewhat
resolved, and I'm trying to understand what could have caused the problem
to occur in the first place. Below is a full chronicle of an incident we've
ran into.
At some point we realized almost no new data was coming in
On 2018-01-29 06:36:41 -0700, David G. Johnston wrote:
> On Mon, Jan 29, 2018 at 1:37 AM, Robert Zenz
> wrote:
>
> Documentation, bug report, mailing list discussions,
> something like that. In particular I'm interested in the questions:
>
> * Why are they required in combination wi
On 2018-01-30 08:40:11 +, Robert Zenz wrote:
> On 30.01.2018 03:07, David G. Johnston wrote:
> > So, my first pass at this.
>
> Nice, thank you.
>
> > + These are of particular use for client software to use when executing
> > + user-supplied SQL statements and want to provide try/catch be
Hi,
unfortunately your message is missing some pretty important information,
like for example which OS you're running, what PostgreSQL version are
you using (and if you built it on your own or installed from some
package repository).
Also, you mention replicas. What type of replication are you us
On Tue, Jan 30, 2018 at 1:40 AM, Robert Zenz
wrote:
> On 30.01.2018 03:07, David G. Johnston wrote:
> > So, my first pass at this.
>
> Nice, thank you.
>
> > + These are of particular use for client software to use when executing
> > + user-supplied SQL statements and want to provide try/catc
On 01/31/2018 09:56 AM, Eugene Pirogov wrote:
Hi,
We've experienced a DB incident related to WAL. The issue is now
somewhat resolved, and I'm trying to understand what could have caused
the problem to occur in the first place. Below is a full chronicle of an
incident we've ran into.
At some
On Wed, Jan 31, 2018 at 12:32 PM, Stefan Blanke <
stefan.bla...@framestore.com> wrote:
> >
> > I'll bet you it's not that. It's quite unlikely that would fail with
> > exactly 1GB request size. It seems much more like a buffer that we keep
> > to be power of 2. The question is which one.
>
> I had
On 01/31/2018 09:51 PM, Jan Wieck wrote:
>
>
> On Wed, Jan 31, 2018 at 12:32 PM, Stefan Blanke
> mailto:stefan.bla...@framestore.com>> wrote:
>
> >
> > I'll bet you it's not that. It's quite unlikely that would fail with
> > exactly 1GB request size. It seems much more like a buffe
> In my case the upgrade routines run migration scripts which modify a
> database schema. Besides that I have a bunch of SQL files with the
> schema that can be used to initialize a new database.
Why not just update the proc's, etc, that depend on the changes?
--
Steven Lembark
On Wed, Jan 31, 2018 at 5:45 AM, Konrad Witaszczyk wrote:
> Hi,
>
> I'm considering changing my database schema upgrade routines to recreate
> functions and all objects depending on them (e.g. triggers, views) just
> after
> the database server is started. It would make the routines much simpler
Hello everybody,
I'm one of the maintainers of postgrex [1] - an Elixir client for Postgresql.
We implement the wire protocol and connect directly through tcp. We got a bug
report indicating we got an unexpected ErrorMessage packet in reply to
SSLRequest.
The documentation [2] indicates this c
On Wed, Jan 31, 2018 at 8:52 AM, Alexander Stoddard <
alexander.stodd...@gmail.com> wrote:
> If a table is set to unlogged is it inherently non-durable? That, is any
> crash or unsafe shutdown _must_ result in truncation upon recovery?
>
Yes.
> I can imagine a table that is bulk loaded in a war
On Wed, Jan 31, 2018 at 10:52:38AM -0600, Alexander Stoddard wrote:
> If a table is set to unlogged is it inherently non-durable? That, is any
> crash or unsafe shutdown _must_ result in truncation upon recovery?
Yes, they are designed like that. Upon recovery all unlogged tables are
re-initializ
On Mon, 29 Jan 2018 15:34:18 +0100
Matej wrote:
> Hi Everyone.
>
> We are looking at a rather large fin-tech installation. But as
> scalability requirements are high we look at sharding of-course.
>
> I have looked at many sources for Postgresql sharding, but we are a
> little confused as to sh
Tomas,
Indeed, I haven't put enough detail in the original post. That is a fair
point, thank you. Let me follow up on each of your comments.
unfortunately your message is missing some pretty important information,
> like for example which OS you're running, what PostgreSQL version are you
> using
41 matches
Mail list logo
