On Thu, Oct 6, 2022 at 3:53 PM Bryn Llewellyn wrote:
>
> (3) The PG doc on quote_ident says this in large friendly letters:
>
> Quotes are added only if necessary…
>
>
> Notice "only". I now know that this is very much not the case. You can
> compose an effectively unlimited number of different
> list.pg.ga...@pendari.org wrote:
>
>> b...@yugabyte.com wrote:
>>
>> Does this imply a risk that a future PG version will go against the SQL
>> standard and reject any non-latin name that is free of all punctuation
>> characters, when used in the role of a SQL identifier, unless it's double
> karsten.hilb...@gmx.net wrote:
>
>> b...@yugabyte.com wrote:
>>
>> What we deal with in our ordinary professional work is SQL texts, program
>> source texts, within these, SQL identifier texts, and then the conventional
>> display of the results of SQL and program execution. To emphasize the
On 10/6/22 1:54 PM, Ron wrote:
On 10/6/22 14:32, Adrian Klaver wrote:
On 10/6/22 10:46, Christophe Pettus wrote:
On Oct 6, 2022, at 10:44, Ron wrote:
Sadly, that VM doesn't have nearly enough disk space to hold the
backup folder.
Use file mode, and stream the output via scp/ssh to a
On 10/6/22 2:03 PM, Ron wrote:
On 10/6/22 14:35, Adrian Klaver wrote:
On 10/6/22 09:46, Ron wrote:
On 10/6/22 10:20, Tom Lane wrote:
Because installing new software on production servers requires
hurdles (Service Now change ticket approved by the application
support manager, Delivery
On 10/6/22 14:35, Adrian Klaver wrote:
On 10/6/22 09:46, Ron wrote:
On 10/6/22 10:20, Tom Lane wrote:
Ron writes:
On 10/6/22 09:49, Tom Lane wrote:
Ron writes:
pg_dump 9.6.24
You realize that that version's been out of support for a year?
Yes, which is why I'm dumping from an EOL cluster,
On 10/6/22 14:32, Adrian Klaver wrote:
On 10/6/22 10:46, Christophe Pettus wrote:
On Oct 6, 2022, at 10:44, Ron wrote:
Sadly, that VM doesn't have nearly enough disk space to hold the backup
folder.
Use file mode, and stream the output via scp/ssh to a different machine?
Or Plan B:
On 10/6/22 12:46, Christophe Pettus wrote:
On Oct 6, 2022, at 10:44, Ron wrote:
Sadly, that VM doesn't have nearly enough disk space to hold the backup folder.
Use file mode, and stream the output via scp/ssh to a different machine?
I thought of that, too. Unfortunately, the ssh version in
On 10/6/22 09:46, Ron wrote:
On 10/6/22 10:20, Tom Lane wrote:
Ron writes:
On 10/6/22 09:49, Tom Lane wrote:
Ron writes:
pg_dump 9.6.24
You realize that that version's been out of support for a year?
Yes, which is why I'm dumping from an EOL cluster, and restoring to a
supported version.
On 10/6/22 10:46, Christophe Pettus wrote:
On Oct 6, 2022, at 10:44, Ron wrote:
Sadly, that VM doesn't have nearly enough disk space to hold the backup folder.
Use file mode, and stream the output via scp/ssh to a different machine?
Or Plan B:
1) Use pg_dump 9.6.24 on existing(going
> On Oct 6, 2022, at 10:44, Ron wrote:
> Sadly, that VM doesn't have nearly enough disk space to hold the backup
> folder.
Use file mode, and stream the output via scp/ssh to a different machine?
On 10/6/22 11:48, Christophe Pettus wrote:
On Oct 6, 2022, at 09:46, Ron wrote:
Because installing new software on production servers requires hurdles (Service
Now change ticket approved by the application support manager, Delivery Service
Manager, Engineering Change Board, and a one week
> On Oct 6, 2022, at 10:20, Kaushal Shriyan wrote:
>
> I am not sure if I understand the difference between binary and logical
> replication between PostgreSQL Master and Standby/Slave server.
It's best to review the documentation here:
Thanks Christophe for the email and appreciate it. I am not sure if I
understand the difference between binary and logical replication
between PostgreSQL Master and Standby/Slave server.
Please guide me. Thanks in advance.
Best Regards,
Kaushal
On Wed, Oct 5, 2022 at 11:02 PM Christophe
> On Oct 6, 2022, at 09:46, Ron wrote:
> Because installing new software on production servers requires hurdles
> (Service Now change ticket approved by the application support manager,
> Delivery Service Manager, Engineering Change Board, and a one week lead time
> before installing during
On 10/6/22 10:20, Tom Lane wrote:
Ron writes:
On 10/6/22 09:49, Tom Lane wrote:
Ron writes:
pg_dump 9.6.24
You realize that that version's been out of support for a year?
Yes, which is why I'm dumping from an EOL cluster, and restoring to a
supported version.
But why are you using the
Ron writes:
> On 10/6/22 09:49, Tom Lane wrote:
>> Ron writes:
>>> pg_dump 9.6.24
>> You realize that that version's been out of support for a year?
> Yes, which is why I'm dumping from an EOL cluster, and restoring to a
> supported version.
But why are you using the dead version's pg_dump?
On 10/6/22 09:49, Tom Lane wrote:
Ron writes:
pg_dump 9.6.24
You realize that that version's been out of support for a year?
Yes, which is why I'm dumping from an EOL cluster, and restoring to a
supported version.
Why does pg_restore explicitly create "public" even though public is
+1.
On Tue, Oct 4, 2022 at 5:02 PM Bruce Momjian wrote:
> Would people be interesting in subscribing to a Postgres calendar that
> includes dates for minor releases, final minor release dates for major
> versions, commit fests, and even Postgres events? For example, it could
> include
Ron writes:
> pg_dump 9.6.24
You realize that that version's been out of support for a year?
> Why does pg_restore explicitly create "public" even though public is
> automatically created when the database is created?
We fixed that in v11 (see 5955d9341). Evidently the fix requires an
pg_dump 9.6.24
pg_restore 13.8
Why does pg_restore explicitly create "public" even though public is
automatically created when the database is created?
I noticed that when using "--exit-on-error". It's disappointing, because I
had to remove that option, which caused the restore to ignore
Kouber Saparev writes:
> I noticed that attaching the "_RETURN" rule to a table converts it to a
> view, and the operation is irreversible, i.e. once attached, I cannot drop
> the rule and put the relation back to a table one.
That is an ancient backwards-compatibility hack that you should not
Is there a special reason why masking views behind table partitions is not
allowed?
Trying to do so raises an error:
CREATE RULE "_RETURN" AS ON SELECT TO xxx_20220715 DO INSTEAD SELECT * FROM
yyy WHERE ...;
ERROR: cannot convert partitioned table "xxx_20220715" to a view
Hi teams,
I am a student who are interested in database,and now I want to generate a
call-graph for this database that can help me to understand the structure.(The
project is written in cpp,not only c)
I haved tried the doxygen,but the information that generates is very
incomplete(Even if I
What we deal with in our ordinary professional work is SQL texts, program
source texts, within these, SQL identifier texts, and then the conventional
display of the results of SQL and program execution. To emphasize the point
about resulst display, try "\d s.*" in "\t off" mode. You'll see
On 6 Oct 2022, at 16:04, Bryn Llewellyn wrote:
Does this imply a risk that a future PG version will go against the
SQL standard and reject any non-latin name that is free of all
punctuation characters, when used in the role of a SQL identifier,
unless it's double quoted?
From my perspective
26 matches
Mail list logo
